Repository navigation
Fix component counts and missing entries in HTML reports - #281
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.
Fixes #279.
Component additions and removals shared the
$.componentspath, so deduplication collapsed separate components into one entry per category. The reported example retained only five of 30 component additions.Use component-name paths before deduplication for HTML, Markdown, and summary reports. The example now retains all 30 component entries and reports 47 changes: 46 additions and one modification. Raw tree data and machine-readable JSON output remain unchanged.
Validation:
Browser verification remains incomplete because the browser policy blocked local HTML files. Generated HTML and payload checks pass.