feat(core): Introduce MultiChannelStockLocationStrategy #3243
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
Fixes #2356. This commit introduces a much more sophisticated stock location strategy that takes into account the active channel, as well as available stock levels in each available StockLocation. With v3.1.0 it will become the default strategy.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Addresses #2356.
Breaking changes
This PR replaces the default
stockLocationStrategywith a brand new one. Although technically it means that the default behaviour is different in multi-channel, multi-location setups, this is only because the old default behaviour was very much non-functional in that scenario.All the e2e tests pass, so for the single-location scenario supported by the old default, this new one behaves identically.
Therefore in the release notes we will just include a note about this, and provide instructions on how to get the old behaviour back in the unlikely event that someone knowingly relied upon it.
Checklist
📌 Always:
👍 Most of the time: