Skip to content

Fix component counts and missing entries in HTML reports - #281

Merged
daveshanley merged 1 commit into
mainfrom
codex/issue-279-component-additions
Oct 11, 2026
Merged

daveshanley merged 1 commit into
mainfrom
codex/issue-279-component-additions

Conversation

@daveshanley

Copy link
Copy Markdown
Member

Fixes #279.

Component additions and removals shared the $.components path, 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:

  • Command and full Go test suites pass; vet passes for the affected packages.
  • Regression tests cover additions, removals, duplicate references, path escaping, and OpenAPI 3.2 media types. The count package has 100% statement coverage.
  • Petstore remains at 42 changes and 18 breaking changes.
  • Independent review has no remaining findings.

Browser verification remains incomplete because the browser policy blocked local HTML files. Generated HTML and payload checks pass.

@daveshanley
daveshanley merged commit 1ba377a into main Oct 11, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 HTML report undercounts added components and conflates component types with individual components

1 participant