Skip to content

Conversation

@rvalyi
Copy link
Member

@rvalyi rvalyi commented Mar 14, 2019

standard migration: nothing to be done: same code as version 11 (except version number)

cc @hbrunn @NL66278 @pedrobaeza @sergio-teruel @alexis-via

hbrunn and others added 9 commits March 14, 2019 15:33
Trivial changes:

* Version in README changed
* Version in manifest changed

OCA Transbot updated translations from Transifex

OCA Transbot updated translations from Transifex
…extension. (OCA#804)

* Add list_add operation.
* Add list_remove operation.

OCA Transbot updated translations from Transifex
expression not match the node any more. Fixes OCA#885
*  warning about dynamic context
* import for safe_eval
@alexis-via
Copy link
Contributor

It seems you forgot the update of the version number.

@rvalyi rvalyi force-pushed the 12.0-mig-base_view_inheritance_extension branch from 578d34c to d3e9534 Compare March 14, 2019 20:10
@rvalyi
Copy link
Member Author

rvalyi commented Mar 14, 2019

@alexis-via sorry. I now amended the commit with the right version

@rvalyi rvalyi force-pushed the 12.0-mig-base_view_inheritance_extension branch from d3e9534 to 61a83bb Compare March 14, 2019 21:10
@rvalyi
Copy link
Member Author

rvalyi commented Mar 14, 2019

@alexis-via sorry, I did it wrong as I was in a meeting with Renato. I should not have changed the version in the Transiflex pot commit, so I undo that and I added a new commit for it 61a83bb
Should be good now, sorry again.

@pedrobaeza pedrobaeza added this to the 12.0 milestone Mar 15, 2019
@OCA-git-bot OCA-git-bot mentioned this pull request Mar 15, 2019
32 tasks
@hbrunn
Copy link
Member

hbrunn commented Mar 15, 2019

v12 has its own version of position="move", cf https://github.com/OCA/OCB/blob/12.0/odoo/addons/base/models/ir_ui_view.py#L650 ff and https://www.odoo.com/documentation/12.0/reference/views.html#inheritance-specs (note at the end).

It seems to me both can coexist, and I find the way they have chosen a little bit clumsy, but it serves the same purpose. Should we drop support for position="move" here for consistency or keep it for simpler migrations of modules using it and a imho nicer syntax?

@NL66278
Copy link
Contributor

NL66278 commented Mar 15, 2019

@hbrunn I would people encourage to use the standard Odoo way as much as possible. So keep the position="move" for now, but clearly mark/document it as deprecated.

@pedrobaeza
Copy link
Member

But are they going to conflict having the same name?

@hbrunn
Copy link
Member

hbrunn commented Mar 15, 2019

no, because for Odoo standard, the attribute is supposed to be added to a child of the element you match, in our version it's on the element you match

@pedrobaeza
Copy link
Member

Pretty confusing, isn't it? I prefer to remove it...

@bealdav
Copy link
Member

bealdav commented Mar 29, 2019

Any decision here ?

@tbaden
Copy link
Member

tbaden commented Apr 21, 2019

I would prefer to use odoo core behaviour, but just my opinion. nothing against this feature, but to have both will be quite confusing.

@astirpe
Copy link
Member

astirpe commented May 28, 2019

I would prefer the position="move" removed from this module. Just a preference, not blocking for this.

@ernestotejeda
Copy link
Member

@rvalyi, what conclusion do we get here? What can we do to conclude with this migration?
maybe drop support for position="move" here is good idea, what do you think? ;-)

@hbrunn
Copy link
Member

hbrunn commented Sep 4, 2019

note that since version 9, also the list_{add,remove} parts can be done with Odoo core: OCA/OCB@f962b0f (actually in a nicer way because you can also select a separator) - so if we deprecate the moving, we also should deprecate that

@ernestotejeda
Copy link
Member

note that since version 9, also the list_{add,remove} parts can be done with Odoo core: OCA/OCB@f962b0f (actually in a nicer way because you can also select a separator) - so if we deprecate the moving, we also should deprecate that

Yes, i agree with you @hbrunn 👌

@tsabi
Copy link

tsabi commented Dec 1, 2019

Hi, when will you merge this? A lot of module depends from this.
Thanks, Csaba

@@ -0,0 +1,2 @@
# License LGPL-3.0 or later (http://www.gnu.org/licenses/lgpl.html).
Copy link
Contributor

Choose a reason for hiding this comment

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

Make license lines https:

Copy link
Contributor

Choose a reason for hiding this comment

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

done

Copy link
Contributor

@NL66278 NL66278 left a comment

Choose a reason for hiding this comment

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

I agree that all the methods that are now in standard Odoo should be removed. Either completely, or at least by giving a Deprecated message when still used (to be turned into an Exception in 13.0).

@rvalyi
Copy link
Member Author

rvalyi commented Dec 2, 2019

Hello folks, I dont really use this module myself. So if somebody wants to redo the migration in another PR/another way please feel free to go ahead as I cannot dedicate time to this one these days unfortunately...

@pedrobaeza pedrobaeza changed the title 12.0 mig base view inheritance extension [12.0][MIG] base_view_inheritance_extension: Migration to 12.0 Jan 8, 2020
@alexis-via
Copy link
Contributor

I continued the work of @rvalyi and removed the features which are now native. The readme of the module has been updated. Tests works fine. I also tested it with my PR OCA/account-invoicing#570 which makes use of this module in v12 and it works well. So it's ready to merge now.

Copy link
Member

@bealdav bealdav left a comment

Choose a reason for hiding this comment

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

LGTM

@alexis-via alexis-via force-pushed the 12.0-mig-base_view_inheritance_extension branch from 4a230fd to 61a83bb Compare March 3, 2020 14:13
@alexis-via
Copy link
Contributor

As said by Pedro in the PR for v13, the list_add and list_remove feature is NOT native. So I cancelled my previous commit and push a new commit with only the removal of the move feature.
I took into account all the remarks of the reviewers. So it's now ready to merge.

@pedrobaeza
Copy link
Member

/ocabot merge

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 12.0-ocabot-merge-pr-1529-by-pedrobaeza-bump-no, awaiting test results.

@OCA-git-bot
Copy link
Contributor

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

@OCA-git-bot OCA-git-bot merged commit e481f7a into OCA:12.0 Mar 3, 2020
SiesslPhillip pushed a commit to grueneerde/OCA-server-tools that referenced this pull request Nov 20, 2024
Syncing from upstream OCA/server-tools (16.0)
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.