Amend DFC backorder completely #13000
Draft
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
So that we can use order states programmatically.
Update every single order line to reflect local orders and stock levels. New cases supported: * Add lines for orders created by an admin. * Create backorder line after increase of local line item quantity. * Adjust local stock after variant has been removed from order cycle.
mkllnk
added
the
technical changes only
RaggedStaff
reviewed
Nov 27, 2024
|
|
||
| def self.load_context | ||
| JSON::LD::Context.add_preloaded("http://www.datafoodconsortium.org/") { | ||
| JSON::LD::Context.parse(read_file("context_1.8.2")["@context"]) |
There was a problem hiding this comment.
All releases of the ontology now have a versioned context file associated with them. We should target latest release (currently v1.14.0, soon to be v.1.15.0 for Variants)
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.
What? Why?
Before, we accounted for cancelled orders but not for changed or removed line items. Now we completely re-calculate the backorder and can re-use this logic whenever something changes.
But so far, we still only trigger this when an order is cancelled or when the backorder is completed.
What should we test?
Release notes
Changelog Category (reviewers may add a label for the release notes):
The title of the pull request will be included in the release notes.
Dependencies
Documentation updates