Fixes to 19.0 migration and JS libraries update#7
Fixes to 19.0 migration and JS libraries update#7juppe wants to merge 5 commits intoweinni2000:19.0-mig-base_geoenginefrom
Conversation
Update the geometry string parsing logic to automatically attempt WKB hex loading even if the WKB flag is not explicitly set. This handles cases where a hex string is provided but treated as WKT, falling back to WKT parsing only if hex validation fails.
Upgrades external libraries Chroma.js, Geostats, and OpenLayers to newer versions to ensure compatibility and leverage recent improvements. This includes transition to new folder structures for versioned assets.
Moves OpenLayers, Chroma.js, and Geostats out of the standard asset bundle to a dedicated dynamic loading utility. This centralization prevents potential bundler conflicts and ensures libraries are loaded asynchronously only when required. Updates the GeoEngine renderer and map edit widget to utilize this shared loader for dependency initialization.
There was a problem hiding this comment.
Sorry @juppe, your pull request is larger than the review limit of 150000 diff characters
Updated field label from "Params" to "Params WMS" of params_wms
attribute_field_id domain is updated to use values based on geo_field_id.model_id
|
@weinni2000 What do you think about this approach? If you review and merge this PR into your branch and then update your PR @ oca/geospatial to include these fixes? |
|
@juppe: |
@weinni2000 I can take over. However, I'm not that much of a git wizard so that I would know how to exactly take over from here. We have your fork and your branch and your PR @OCA. Then we have my work that is done on top of yours. What kind if git tricks do we need to do for me to take over? |
|
@juppe: |
Improve WKT vs WKB detection in geometry conversion
Update frontend library dependencies: OpenLayers, Chroma.js, Geostats
Refactor geo library loading to use dynamic imports
Also cherry-picked in the two commits from: OCA#431