Skip to content
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

[16][FIX] rma: qty received and shipped in case of multiple step reception/expedition #553

Merged

Conversation

florian-dacosta
Copy link
Contributor

Remove changes introduced here : ff0e4fb

Because since this commit, the selection of the move previously in this method have evolved, so now, it breaks the quantity received/shipped in the case of chained moves intead of fixing it...

@AaronHForgeFlow @DavidJForgeFlow

@DavidJForgeFlow
Copy link
Contributor

Hi @florian-dacosta,
Thanks for the PR! However, can you add some tests to make sure this isn't breaking any feature?

…n/expedition

Now the moves are filtered and only 1 move of the chain is selected to compute the quantity (the first one for reception and last one for expedition), so we should no longer ignore those to compute the quantities
@florian-dacosta
Copy link
Contributor Author

@DavidJForgeFlow
Sure, I have added a test about qty_received / delivered with multiple steps (chained moves).
The test will fail if you launch on a 16.0 branch. It is fixed in this PR.
Let me know what you think.

Copy link
Contributor

@DavidJForgeFlow DavidJForgeFlow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! @AaronHForgeFlow can you check this also please!

Copy link
Contributor

@AaronHForgeFlow AaronHForgeFlow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this makes sense. Thank you for the tests.

@AaronHForgeFlow AaronHForgeFlow merged commit 7b520fe into ForgeFlow:16.0 Nov 11, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants