Using multiple map interactions #751
Open
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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #751 +/- ##
==========================================
- Coverage 81.92% 81.87% -0.06%
==========================================
Files 238 239 +1
Lines 4853 4872 +19
Branches 1310 1318 +8
==========================================
+ Hits 3976 3989 +13
- Misses 841 847 +6
Partials 36 36
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Because this feature will be added after 3.0, this PR is moved to draft. This PR is still ready to be reviewed, it just shouldn't be merged just yet |
robinmolen
force-pushed
the
feature/2177-map-interactions
branch
from
95cf149 to
2690059
Compare
robinmolen
force-pushed
the
feature/2177-map-interactions
branch
from
2690059 to
56151ac
Compare
robinmolen
force-pushed
the
feature/2177-map-interactions
branch
4 times, most recently
from
bb93058 to
6a5999f
Compare
Added leaflet-draw and react-leaflet-draw as dependencies. These allow easy user interactions with the leaflet map
…ead of coordinates The map component now uses and stores geoJson data, instead of coordinates. This means we can display and work with multiple shapes. One important change is that geoJson saves coordinates as lng-lat, instead of lat-lng
…ponent property With the new property `interactions` the component can defined the possible map interactions. Currently supporting 'marker', 'polygon' and 'polyline'
…tories for map component
Due to some formio magic, the `resetValue` flag is needed when performing the `setValue` call. Without this flag it isn't allowed to set a field value to `null` or `undefined`.We also need to use the value `null`, instead of `undefined`. This because setting the value to `undefined` isn't reflected as a value change (what we need, to re-render the component). This is described in node_modules/formiojs/components/_classes/component/Component.js:2524
…eoJson geometry Because we won't support circle shapes (due to geoJson and the backend registrations not supporting this type), we no longer need the geoJson feature `properties`. Because we don't use `properties` for anything else, it doesn't make sense to save it
robinmolen
force-pushed
the
feature/2177-map-interactions
branch
from
6a5999f to
c206b88
Compare
Bundle ReportChanges will increase total bundle size by 77.39kB (1.65%) ⬆️. This is within the configured threshold ✅ Detailed changes
|
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.
Part of open-formulieren/open-forms#2177
This allows users to interact with the map using multiple tools: markers (the interaction that is already being used), polygons and polylines. With the aim to give users more accurately control. Using the new
interactionsproperty every tool can be included or excluded separately. By default, only the marker will be available to users (conform the current functionality)The different tools result in different data. To accommodate this the data of the component has been changed from an array of numbers, to a geoJson object.
All previously existing functionality has been updated to work with this new data format. This includes:
To accommodate the polyline and polygon, the center point of a shape is used as the centering point. This changes nothing for the marker shapes
This currently also works for the polyline and polygon. Because these shapes consist of multiple points/coordinates, the center point of these shapes is used as the
search nearby addresscoordinates