fix: Inventory is set to NaN in rare circumstances based on Migrations
#4946
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.
Impact: minor
Type: bugfix
Issue
While not confirmed to be the only way this happens, it seems that if a user has not run
Migration 51yet, when they pull in the changes that come along withMigration 56,inventoryQuantity/inventoryInStockgets set toNaN.If a codebase is already past
Migration 51when the changes that includeMigration 56are pulled in, everything is OK.Solution
Create a new migration,
Migration 57, to make sure inventory in never set toNaNwhen a user has already runMigration 51. Also, go back and fixMigration 51to address this issue for users who haven't run it yet.Breaking changes
None
Testing
inventoryInStockorinventoryAvailableToSellis set toNaNin theProductsorCatalogcollection