Cleanup leaflet from leafletData after scope.$destroy #312
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
houqp
added a commit
that referenced
this pull request
Mar 6, 2014
Cleanup leaflet from leafletData after scope.$destroy
Contributor
|
thank you for the fix :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On app that constantly initializes new maps and custom directives on top of it had problems when directives launched before map was ready. Directives then added layers to old, already destroyed map. With this patch, directive detects if it's destroyed from scope's $destroy event and then unresolves itself from leafletData. This could and should be done for other directives too, but for most use cases this should be enough.
Issue discussion at #299