Conversation
BundleDetails rows are no longer sub-numbered under their parent bundle (1.01, 1.02, ...); every emitted line now takes the next number in one running sequence. Comment placement is unchanged (Max Qty only on Bundle/ Part Number lines). Updated File1 tests, regenerated its goldens, and refreshed the HPE format spec + output mapping docs.
…quence Bundle Detail rows (HP Bid) and component rows (OneConfig) are no longer sub-numbered under their parent (1.01, 1.02, ...); every emitted line now takes the next number in one running sequence. Comment placement is unchanged (Max Qty only on Part Number/Bundle lines). Updated parser tests, regenerated the affected goldens, and refreshed the HP format specs + output mapping docs.
…sequence Child/component rows are no longer sub-numbered under their parent (1.01, 1.02, ...); every emitted line now takes the next number in one running sequence. Since the sequence no longer encodes the hierarchy, tests now distinguish parent from child by cost (parents priced > 0, children dropped to 0). Updated parser tests, regenerated the three Lenovo goldens, and refreshed the Lenovo format specs.
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.
Summary
Flattens the output Item column (
line_sequence) so every emitted line takes the next number in a single running sequence (1, 2, 3, …) instead of sub-numbering bundle/config components asparent.NN(1.01,1.02, …). Applied across all parsers that previously nested:2, 3, …after the parent1.Zebra was already flat and is unchanged.
Notes
Max Qtystill appears only on Part Number/Bundle lines.> 0; children dropped to0, exported as the0.0001sentinel). Lenovo tests were reworked accordingly.Verification
dotnet test→ 178 passed.output_mapping.md,project_memory.md.