-
-
Notifications
You must be signed in to change notification settings - Fork 485
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] mrp_bom_attribute_match #933
base: 16.0
Are you sure you want to change the base?
Conversation
523d47b
to
c1e4c92
Compare
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
@mymage If you are willing to reopen the PR I can make sure it gets merged this time (+2 reviewers) (although some PRs with fixes have been merged in between) |
@giarve Thanks for your help. |
/ocabot migration mrp_bom_attribute_match |
Thanks @grindtildeath. |
843a591
to
f3fe92b
Compare
a32e85c
to
33ae3a0
Compare
Currently translated at 83.3% (15 of 18 strings) Translation: manufacture-14.0/manufacture-14.0-mrp_bom_attribute_match Translate-URL: https://translation.odoo-community.org/projects/manufacture-14-0/manufacture-14-0-mrp_bom_attribute_match/hr/
Currently translated at 100.0% (16 of 16 strings) Translation: manufacture-14.0/manufacture-14.0-mrp_bom_attribute_match Translate-URL: https://translation.odoo-community.org/projects/manufacture-14-0/manufacture-14-0-mrp_bom_attribute_match/it/
… of a component_template_id.
Notes: * `_get_product2bom` renamed to `_bom_find` * Test case `test_manufacturing_order_2`: * No longer check for "Add some materials to consume before marking this MO as to do.", as it's already supported in core since odoo/odoo@bf5e1debf
The check expects a single record, so it should be processed accordingly.
These methods shouldn't be exposed to xmlrpc.
The same result can be achieved with a computed field. Moreover, we have one already in odoo core. Originally it was a related field, but we can change it to a computed and add our extra logic there.
Instead of updates triggered by onchanges or writes, use constraints to execute all checks, and a computed field for `match_on_attribute_ids`
There isn't any reson to depend on it.
Currently translated at 100.0% (19 of 19 strings) Translation: manufacture-15.0/manufacture-15.0-mrp_bom_attribute_match Translate-URL: https://translation.odoo-community.org/projects/manufacture-15-0/manufacture-15-0-mrp_bom_attribute_match/it/
Currently translated at 100.0% (19 of 19 strings) Translation: manufacture-15.0/manufacture-15.0-mrp_bom_attribute_match Translate-URL: https://translation.odoo-community.org/projects/manufacture-15-0/manufacture-15-0-mrp_bom_attribute_match/it/
33ae3a0
to
5ee00e3
Compare
No problem. I made a new branch migrating from 14.0 which has the latest changes. I still have to test everything but with WinMerge it looked really similar to 15.0 https://github.com/wvbs/manufacture/commits/16.0-mig-mrp_bom_attribute_match/ You can use this branch from now on. I added your changes, but it has all the fixes for 14.0. We will have to see if tests pass (EDIT: they don't, I messed up somewhere when merging). Something else to consider is that we must also migrate mrp_account_bom_attribute_match with a new PR (EDIT: #1200) I didn't want to force push on this PR without permission |
You are moving me to "new level" of cooperation: thank for your trust, I will do my best to complete this task. |
More tests are passing now. you can switch the branch in this PR to the new one if you wish. mrp_report_bom_structure.py has to be rewritten entirely as the function names that were being overwritten are different in 16.0 |
No description provided.