Open rrebollo opened 4 weeks ago
/ocabot migration sale_mrp_bom
@pedrobaeza sorry to bother U, the failing test is pointing to pre-commit stuff which aren't in the addon I'm upgrading so what can I do about it?
That's because you have updated the copier template in this PR, and thus, new linter requirements. You have to either not update the copier template, or update it, and fix the linter new complaints.
I've tested the module, and overall it performs well, as it does in other versions. However, I suggest enhancing the bom_id field by extending the domain to allow BOM selection only when the product is configured with the right routes. Specifically, the product should have either:
This improvement would help ensure that defining a BOM on the Sales Order leads to a Manufacturing Order upon confirmation (otherwise it only serves to have the reference), other, aligning with expected behavior. I noticed this feature isn’t present in v16 either, so this adjustment could done across versions.
What do you think?
That's because you have updated the copier template in this PR, and thus, new linter requirements. You have to either not update the copier template, or update it, and fix the linter new complaints.
I had to. The repo template has fixed node to v14 and it was raising eslint invalid syntax errors. Same for autoflake and flake8 hooks for pre-commit. The first one was raising "no module name distutils", the second one "AttributeError: 'EntryPoints' object has no attribute 'get'".
I'll fix the pre-commit complaints.
LGTM, Can you squash the translation commits?
LGTM, Can you squash the translation commits?
Better now?
@renatonlima @hailangvn sorry to bother U guys. Would U be so kind to maybe do a quick code review of this addon. I think U were involved with it.
@rousseldenis would U be so kind to review this?. I'm available to review anything U suggest me.
@rrebollo Thanks for this. Could you do a PR with your changes on repo configuration and fixes commit ? I will merge it quickly but it will easy the review part. Thanks
@rousseldenis the commit updating repo template and pre-commit hooks went to #3411. Better now?
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). 🤖
Reusing work from #2234 .
Currently refactoring tests.