-
-
Notifications
You must be signed in to change notification settings - Fork 805
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
[16.0][MIG] purchase_order_qty_change_no_recompute: Migration to 16.0 #2193
[16.0][MIG] purchase_order_qty_change_no_recompute: Migration to 16.0 #2193
Conversation
2027465
to
197bee4
Compare
…ly quantity has changed in sale order line
[UPD] Update purchase_order_qty_change_no_recompute.pot [UPD] README.rst
purchase_order_qty_change_no_recompute 15.0.1.0.1
Translated using Weblate (Spanish) Currently translated at 100.0% (1 of 1 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-purchase_order_qty_change_no_recompute Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-purchase_order_qty_change_no_recompute/es/ [UPD] README.rst
…ement - Include context keys for avoiding mail operations overhead. [BOT] post-merge updates
197bee4
to
3f5d9f9
Compare
After changing the approach of Problem: Previously (v15) there was a context that allowed (in the tests) to omit onchange the relative to
How could we add a context (or similar) in the Ping @pedrobaeza |
- Improve documentation - Improve tests - Put it as rebel module TT46595
02449f4
to
b39b2c6
Compare
In this case, there's no other solution except put it as rebel module. I have push an update branch with the following changes:
|
/ocabot migration purchase_order_qty_change_no_recompute |
# Monkey-patching of the method | ||
Field.get_depends = get_depends |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you study the possibility to hook into the model _setup_fields
method and use a similar estrategy to the one in _pop_field
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I already did. It doesn't serve, as the depends is something dynamic that can be expanded through other modules.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, the main issue here is that this technique can be use only once? Am I wrong?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I'm afraid
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although maybe subsequent monkey patches will work over the previous replaced method...
/ocabot merge nobump |
Hey, thanks for contributing! Proceeding to merge this for you. |
Congratulations, your PR was merged at 6f0b690. Thanks a lot for contributing to OCA. ❤️ |
Superseed #1886
Changes done:
price_unit
,name
anddate_planned
fields use the same compute method (and therefore the same depends).@Tecnativa TT46595