[19.0][MIG] stock_request_partner: Migration to 19.0 - #99
Open
alan196 wants to merge 12 commits into
Open
Conversation
Currently translated at 100.0% (7 of 7 strings) Translation: stock-logistics-warehouse-14.0/stock-logistics-warehouse-14.0-stock_request_partner Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-warehouse-14-0/stock-logistics-warehouse-14-0-stock_request_partner/it/
…hen is created from an order
OCA-git-bot
added
series:19.0
mod:stock_request_partner
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Migration of
stock_request_partnerto 19.0.Supersedes #59 (closed as stale). Based on the module history from the 17.0 branch, including the fix to allow saving the partner on a stock request created from an order.
Changes for 19.0:
_prepare_procurement_valuesoverride:procurement.groupwas replaced bystock.referencein core, so the partner is now passed directly in the procurement values and propagated to the picking.tree→list, updatestock_request_idscontext to match the 19.0 base view (default_reference_ids,default_route_id) plusdefault_partner_id.setUpClass, create partners instead of relying on demo data, use a sharedstock.referencefor the multi-line order test (required in 19.0 to group moves into a single picking) and assert the partner on the resulting picking.self.env._()and remove the old 17.0 migration script.