Hover feature #779
Merged
Hover feature #779
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
|
the vector tile styling must have a merge of all features with the same id. |
mbarbeau
added a commit
that referenced
this pull request
Nov 16, 2020
* feat(vectorLayer) add a hover directive #773 * feat(layerVector.hover) add hover for layer vector and fix #765 * feat(map.hover) delete hover screen on single click * feat (map.hover) fix lint * Delete mapboxStyle-covid.json no need ... * Delete mapboxStyle-covidcomplet.json no need ... * Update hover-routing.module.ts Co-authored-by: Marc-André Trottier <trottier.marcandre@msp.gouv.qc.ca> Co-authored-by: Marc-André Barbeau <marc-andre.barbeau@msp.gouv.qc.ca>
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.
Please check if the PR fulfills these requirements
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
hover on vector layer
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications:
Other information:
tested with WFS (Point, Line and Polygon) and VectorTile (Polygon).
example added (WFS Point and Polygon)