Skip to content
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

[17.0][MIG] base_geoengine: Migration to 17.0 #368

Merged
merged 445 commits into from
Sep 27, 2024

Conversation

peluko00
Copy link

@peluko00 peluko00 commented Apr 25, 2024

Module migrated to version 17.0

cc https://github.com/APSL 154489
@miquelalzanillas @lbarry-apsl @javierobcn @mpascuall please review

To do:

  • As an admin, if I change the domain of a layer with the filter button then the change are persisted in database.
  • As a user, if I change the domain of a layer with the filter button then the change are not persisted in database. There are just the changes in the display.
  • As an admin,If the geoengine view is in edit mode, I can create new records by drawing them in the view.

yvaucher and others added 30 commits April 25, 2024 15:54
…isplay values of selection field instead of technical value in info map box in geoengine view
The feature to set a symbol with symbol_url or symbol_binary on vector
layers was broken. This replace those fields by a new object vector
symbol on which you can specify which symbol to use depending on a field
value.
geo_contains calls St_Contains SQL search.

Plus fix search to set SRID to avoid mixin srid issue.
And extract Swisstopo to move it in a new module
Otherwise partial value is interpreted as context and it will fails on
Odoo loading
…lways need to zoom out to get useful informations
@OCA-git-bot
Copy link
Contributor

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). 🤖

1 similar comment
@OCA-git-bot
Copy link
Contributor

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). 🤖

@mostafabarmshory
Copy link

Any update?

@peluko00

@peluko00
Copy link
Author

Any update?

@peluko00

I'll continue with this module maybe the next month

@mostafabarmshory
Copy link

@peluko00

Tx to your commit. Seams everything is ok to merge, is`n it?

@peluko00
Copy link
Author

@peluko00

Tx to your commit. Seams everything is ok to merge, is`n it?

Not yet, they are some bugs to solve

@mostafabarmshory
Copy link

@peluko00

Your last commit fix unit test. So we are ready to merge with the branch.

Is there any bug or issues?

I check it with odoo 17 manually and every thing seams ok.

Let me know if there is any issue, pleas.

BTW, I can help you to finish it,

TX to your work, hope be fine

@peluko00
Copy link
Author

@peluko00

Your last commit fix unit test. So we are ready to merge with the branch.

Is there any bug or issues?

I check it with odoo 17 manually and every thing seams ok.

Let me know if there is any issue, pleas.

BTW, I can help you to finish it,

TX to your work, hope be fine

Yes, the bugs are in the TODO description of this PR. If you wanna to solve that make a pr to merge into my branch. Thanks in advance

@@ -40,24 +44,85 @@ export class GeoengineController extends Component {
offset: offset,
limit: limit,
total: count,
onUpdate: async ({offset, limit}) => {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There might be a mistake here, the parameter names must be the same that odoo is using: offset and limit. If they don't match the pager can't be updated accordingly.
I could swear this was working when I checked it, has it been changed recently?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, thanks!

>
>
Co-authored-by: Antoni Marroig Campomar <[email protected]>
Co-authored-by: Red Butay <@reichie020212>
Co-authored-by: Miquel Alzanillas <[email protected]>
Co-authored-by: Sergio Sancho <[email protected]>
"
@peluko00
Copy link
Author

@dreispt can you review please

@OCA-git-bot
Copy link
Contributor

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). 🤖

@dreispt
Copy link
Sponsor Member

dreispt commented Sep 27, 2024

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 17.0-ocabot-merge-pr-368-by-dreispt-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit d08686f into OCA:17.0 Sep 27, 2024
7 checks passed
@OCA-git-bot
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.