Define annotation order #523
Merged
Conversation
This file contains 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
|
maybe it would be better to use |
|
@andrea689 Changed it, now the enum naming is fill not polygone. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello @tobrun
Here is a merge request regarding an existing issue marked as enhancement:
Circle always on top of Symbols #483
Added an optional list of "AnnotationType" to define the order in which the layers should be added on map.
Whenever the list is not passed in the mapbox widget, the default behavior (already in the current master branch) is applied,
which means the old users of the package can update their project without any action to have their apps running as usual.
Also added an AnnotationOrder example page in the example project of the repo so you can easily test and see the changes.