-
Notifications
You must be signed in to change notification settings - Fork 6
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
shopfloor: ensure that confirmation email is sent when moves are validated #53
shopfloor: ensure that confirmation email is sent when moves are validated #53
Conversation
012496a
to
f4b058e
Compare
I'd not have taken this approach that needs to pass a context key: almost sure we'll forget to do it on new calls to |
@@ -207,7 +207,8 @@ def _set_destination_and_done(self, move, scanned_location): | |||
# when writing the destination on the package level, it writes | |||
# on the move lines | |||
move.move_line_ids.package_level_id.location_dest_id = scanned_location | |||
move._action_done() | |||
# FIXME: '_sf_no_backorder' was not passed in the context, is it expected? |
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.
Perhaps. Maybe. I don't know.
Originally, this scenario was meant to move a picking with a single package, the behavior for other uses cases are undefined (to my knowledge).
I'll do as you suggest, it's safer. |
@guewen New approach pushed as fixup |
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.
Nice, great to have added checks in the tests
I let some FIXME in the code regarding the existing calls to
move._action_done
without the_sf_no_backorder
context key, I don't know if it was what we wanted when this code has been written or if it needs to be updated/fixed now?Issue 1215
ping @guewen