[Map] Add possibility to configure extra options

[dannyvw]

Q	A
Bug fix?	no
New feature?	yes
Docs?	yes
Issues	Fix #...
License	MIT

TODO

• Add/fix tests
• Add docs
• Rebase when [Map] Add option to configure attribution and zoom control #2792 is merged

Related to #2445 (comment)

Usage:

new LeafletOptions(extra: ['maxZoom' => 1])

[carsonbot]

It looks like you unchecked the "Allow edits from maintainer" box. That is fine, but please note that if you have multiple commits, you'll need to squash your commits into one before this can be merged. Or, you can check the "Allow edits from maintainers" box and the maintainer can squash for you.

Cheers!

Carsonbot

[github-actions]

📊 Packages dist files size difference

Thanks for the PR! Here is the difference in size of the packages dist files between the base branch and the PR.
Please review the changes and make sure they are expected.

File	Before (Size / Gzip)	After (Size / Gzip)
Map (Bridge Google)
map_controller.d.ts	2.73 kB / 828 B	2.78 kB+2% 📈 / 840 B+1% 📈
map_controller.js	11.18 kB / 2.53 kB	11.21 kB0% / 2.53 kB0%
Map (Bridge Leaflet)
map_controller.d.ts	2.04 kB / 672 B	2.07 kB+2% 📈 / 678 B+1% 📈
map_controller.js	9.71 kB / 2.59 kB	9.74 kB0% / 2.6 kB0%

[smnandre]

As this is serialized, I guess we should make some minimal type check on the content of extra, no ?

cc @Kocal

[dannyvw]

@smnandre @Kocal Do you have something in mind?

[Kocal]

extra is already used for Marker and cie to let the developper pass extra data from the back to the front, but the difference with the actual system is that extra are not used by UX Map, these extra data are only used in ux:map:* events.

Instead, I suggest you to implement rawOptions on Map options front-side, nothing should be modified backend-side.

Thanks!

[dannyvw]

extra is already used for Marker and cie to let the developper pass extra data from the back to the front, but the difference with the actual system is that extra are not used by UX Map, these extra data are only used in ux:map:* events.

Instead, I suggest you to implement rawOptions on Map options front-side, nothing should be modified backend-side.

Thanks!

If we only change the front-side how can we set options in the backend which are passed to the front? We want to set some options to the map configuration based on configuration from Symfony DI. Example: for the vector layers we need to pass a layerName and apiKey.