Fix/00459 measurements touch bug snapping v2 #472
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
* typescript build of measure path * all typescript measurement lib * new watch build target * infobox moved out of portals lib * delete measurement playground * remove dead code * wip block leaflet draw touch events * fix touch issue * code cleanup * unified snapping hook * draw update guide to active snapping point * remove old InfoBoxMeasurement in commons/cismap lib * clean up types in measurements * move per measurement state into the hook * sync labels with snap * remove logging in geoportal prod builds * fix alkis desktop measurement topic map ref handling * limit snapping by zoom level * fix typing for snapping and deduplicate extraction
|
View your CI Pipeline Execution ↗ for commit 0b1370d
☁️ Nx Cloud last updated this comment at |
🚀 Deployed
|
🚀 Deployed
|
🚀 Deployed
|
🚀 Deployed
|
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.
merged pr #468 was reverted
this featurebranch / PR should reproduce the problematic behaviour that was introduced in the dev branch and was reverted
by me with 72fba78
forced deploy 0