-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding map interaction config #198
Conversation
1644d74
to
e7254fd
Compare
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I can say, it seems good to me. I would add though some stories for the interactions (not necessarily tests, but just to have the appearance).
The map component stories do show the configuration, but the choice doesn't have a visual representation. |
56ca3aa
to
72b3cc2
Compare
This PR can be reviewed (this includes some chromatic changes that also have to be reviewed) In the formio-builder a new map component configuration option was added: In the form builder map component preview you can test/use the active interactions. |
ff16d26
to
d6949a6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move all of the map settings to a separate tab? Tab title can be "Map settings" or just "Settings", and would come after the "Validation" tab. I think the "Basic" tab is getting too clutter.
Specifically, this means the fields:
- Use globally configured map component settings
- Map configuration (and re-label this to "Initial focus" or something like that)
- Tile layer
- Available interactions
faf26ff
to
9118592
Compare
d8aaa90
to
bbd232a
Compare
bbd232a
to
a684b73
Compare
Both changes are needed for the leaflet-draw and react-leaflet-draw dependencies. leaflet-draw uses images for the different markers, which are included in the css. For this to work with the scss build, .png and .svg files use the dataurl loader https://esbuild.github.io/content-types/#data-url Typescript errors in the react-leaflet-draw dependency caused a typescript validation/error, which shouldn't happen. Using `skipLibCheck` in the tsconfig.json type issues in the node_modules folder are ignored
The React-leaflet-draw package seems abandoned. As such, a fix for the typescript issue (alex3165/react-leaflet-draw#188) probably won't happen anytime soon The .patch file, in `/patches`, contains the fix needed for the react-leaflet-draw index.d.ts file. The problem with this solution, is that this only solves it for this project. If we introduce typescript to the SDK (or any other project using `react-leaflet-draw`), this problem will need to be solved again
…teractions are disabled
6856d22
to
f570ae1
Compare
Part of open-formulieren/open-forms#2177
This relies on a update to the types repo: open-formulieren/types#62