Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the bug that Layer's invalidateAttribute get called for CompositeLayer #421

Merged
merged 2 commits into from
Mar 14, 2017

Conversation

howtimeflies0
Copy link

, which has no AttributeManager so no attribute to invalidate;
Clean up the accessor and prop names for Polygon layer and GeoJson layer

…ich has no AttributeManager so no attribute to invalidate);

Clean up the accessor and prop names for Polygon layer and GeoJson layer;
Copy link
Collaborator

@ibgreen ibgreen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -7,7 +7,15 @@ export default class CompositeLayer extends Layer {

// initializeState is usually not needed for composite layers
// Provide empty definition to disable check for missing definition
initializeState() {}
initializeState() {

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I could go either way on the braces but I don't think we need an empty line

// No-op for the invalidateAttribute function as the composite
// layer has no AttributeManager
invalidateAttribute() {

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

@howtimeflies0 howtimeflies0 merged commit 629e32d into master Mar 14, 2017
@howtimeflies0 howtimeflies0 deleted the invalidate-attribute-composite-layer branch March 22, 2017 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants