Define which annotations consume tap events (Multiple annotations on click area management) #575
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 mentioned here: #563
Added an optional list of "AnnotationType" to define which annotation(s) have to consume tap events.
If FALSE, there is both AnnotationClick + MapClick launched
If TRUE, there is only AnnotationClick.
It's very useful to have FALSE in case of multiple Annotations at the click.
Whenever the list is not passed in the MapBox widget, the default behavior (already in the current master branch) is applied (consumeTapEvents = true to all annotations), which means the old users of the package can update their project without any action to have their apps running as usual.