Repository navigation
fix(catalog): resolve allergens through nested subassemblies - #53
Merged
Merged
Conversation
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
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.
Products now derive allergens from the same recursively flattened material list used for batch snapshots. Allergens in subassemblies are included, sorted, and deduplicated, keeping finished-product and batch-label declarations consistent.
The shared traversal now loads components at every depth and tracks the root product in its cycle guard. Previously nested BOMs were fetched without their components, silently omitting nested materials from the persisted rollup. This also makes nested material quantities available to batch consumption and ingredient snapshots.
Closes #49.
Validation: