[14.0][MIG] stock_putaway_hook #772
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add hooks allowing modules to add more putaway strategies.
It adds hooks to the core putaway method
``StockLocation._get_putaway_strategy()`` allowing to plug other
strategies and makes the selector fields in the tree views dynamic
(required/readonly).
The fields_view_get override is to handle a tricky issue:
By default, the product_id field as such attrs:
"{'readonly': [('category_id', '!=', False)], 'required': [('category_id', '=', False)]}"
And the category_id field:
"{'readonly': [('product_id', '!=', False)], 'required': [('product_id', '=', False)]}"
If we add a new field "route_id", we want to extend the domains to
include it, such as:
"{'readonly': ['|', ('category_id', '!=', False), ('route_id '!=', False)],
'required': [('category_id', '=', False), ('route_id', '=', False)]}"
And every new field will need to be added in the product_id and
category_id field, but also in the other fields (exemple, if we add a
"foo_id" field, it needs to be added in the attrs of "route_id"), which
isn't possible with the extension mechanisms of the XML views.
The solution provided by this module is that new fields must have the
{'exclusive_selection': True} in the options attribute, and an override
of fields_view_get automatically generates the attrs for all these
"exclusive" fields.
The code here will be tested by `stock_putaway_by_route` in a follow-up
commit.
The module matching a putaway rule by a route can now: * find a putaway rule by the route related to a stock move * or a route related to the product on the move The changes required to enable this feature: * In stock_putaway_hook: in the part that match the value, support "in" when the value is a container (recordset, list, tuple), so we can pass product.route_ids (and match any route set on a put-away rule) * In stock_putaway_by_route, in the various parts where `StockLocation._get_putaway_strategy()` is called, propagate the product's routes as well * In StockMoveLine.onchange_product_id, remove the computation based on self.move_id: it cannot change.
|
ping @guewen |
guewen
approved these changes
Jan 26, 2021
bguillot
approved these changes
Feb 4, 2021
hparfr
force-pushed
the
14.0-mig-stock_putaway_hook
branch
from
667ed2b
to
ddf3b6f
Compare
|
This PR has the |
|
Force pushed to make pre-commit happy. |
|
@rousseldenis can you please merge ? |
|
/ocabot merge nobump |
|
What a great day to merge this nice PR. Let's do it! |
|
Congratulations, your PR was merged at 30ce269. Thanks a lot for contributing to OCA. ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.