[18.0][MIG] base geoengine: Migration to 18.0

[cormaza]

Standard migration, refactored some methods with new version

Supersed: #386

[yterrettaz]

I am testing this pull request from a functional perspective within the Odoo GeoEngine module. It includes geographic views on a specific object using OSM raster layers. Projections, spatial filters, and geometry types (polygon and point) have been successfully verified during my tests

[Scuottolinx]

Hi, I tested the plugin, and it doesn't behave as it should.
If I create combined vectors using the model_id and model_domain attributes, the result isn't 100% correct:

• the points on the map are displayed correctly (OK)
• the detail of individual points, when clicking on a point, is always the same, regardless of the selected point (KO)

Any idea why?

Furthermore, the vector filter in the interface displays this error message when clicked:
Uncaught Promise > Invalid props for component 'DomainSelector': 'domain' is undefined (should be a string)

[Scuottolinx]

Hi, I solved my problem:

The detail of individual points, when clicking on a point, is always the same, regardless of the selected point (KO).

just add the field to

Uncaught Promise > Invalid props for component 'DomainSelector': 'domain' is undefined (should be a string).

This error is due to the fact that the Dialog in Odoo 18 has changed, and therefore in:

• layers_panel.esm.js, I had to add the "domain" and "onConfirm" attributes.
• In the DomainSelectorGeoFieldDialog, I obviously defined the same properties.

Maybe it can be useful for a new commit :)

[cormaza]

Hi, I solved my problem:

The detail of individual points, when clicking on a point, is always the same, regardless of the selected point (KO).

just add the field to

Uncaught Promise > Invalid props for component 'DomainSelector': 'domain' is undefined (should be a string).

This error is due to the fact that the Dialog in Odoo 18 has changed, and therefore in:

• layers_panel.esm.js, I had to add the "domain" and "onConfirm" attributes.
• In the DomainSelectorGeoFieldDialog, I obviously defined the same properties.

Maybe it can be useful for a new commit :)

I will review and back with solution

[yvaucher]

LGTM code review only

Great work there, and indeed seems more integrated than #386 for the expressions adaptations to odoo core.

[yvaucher]

/ocabot migration base_geoengine

[OCA-git-bot]

The migration issue (#379) has not been updated to reference the current pull request because a previous pull request (#386) is not closed.
Perhaps you should check that there is no duplicate work.
CC @weinni2000

[yvaucher]

/ocabot merge nobump

[OCA-git-bot]

On my way to merge this fine PR!
Prepared branch 18.0-ocabot-merge-pr-403-by-yvaucher-bump-nobump, awaiting test results.

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[OCA-git-bot]

Congratulations, your PR was merged at d04616a. Thanks a lot for contributing to OCA. ❤️