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.
ol.Collection objects trigger "add" and "remove" events when element are added to, and removed from, the collection. This is very useful; to be notified when layers are added/removed to/from the map for example. Currently, applications using ol.js can register "add" and "remove" listeners, but they cannot get a reference to the element to which "add" and "remove" events pertain. Quite annoying. This PR adds a getElement method to ol.Collection, and export it.