-
Notifications
You must be signed in to change notification settings - Fork 2
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
[4613][ADD] quality_control_oca, quality_control_stock_oca #139
base: 16.0
Are you sure you want to change the base?
Conversation
c1f0c4c
to
3e47632
Compare
…or confirmed moves This commit adds the timing field in the QC trigger line to enable following scenarios: - When timing is 'Before', an inspection is generated wfor each related move when a picking with the trigger is confirmed. - When timing is 'Plan Ahead', a 'Plan' inspection is generated for each related move when a picking with the trigger is confirmed. A plan inspection is just a plan, and cannot be updated except for the date. A plan inspection gets converted into an executable inspection once the picking is done.
3e47632
to
d87bfa4
Compare
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.
Code Review: LGTM
924bf9b
to
766dd03
Compare
Wasn't sure the approach of the last commit to avoid the CacheMiss error was the correct one. @AungKoKoLin1997 Can you please help check. I was getting errors of the following kind from
|
res = super()._action_confirm(merge=merge, merge_into=merge_into) | ||
for move in self: |
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.
@yostashiro I understand the intention of using @lru_cache()
decorator for get_qc_trigger
.
But I still don't understand why we can't use for move in res
instead of checking picking_type_id
in cache.
I think using confirmed moves instead of self is more structured and avoid unnecessary issues.
4f1a390
to
0ed43b8
Compare
4613
Supersedes #136 and #137.