Report output improvements and a JSON renderer for the MDM#85
Merged
Conversation
… analyzer-report.txt detail-only
rousso
changed the title
yfanti
approved these changes
Jun 17, 2026
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
2 participants
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.
Report-output improvements to the analyzer, plus a JSON renderer for programmatic consumers.
Report output
Title banner — the console and both report files now open with a banner carrying the SDK version, the analyser's own version, and the run timestamp (UTC).
--verboseremoved — the console always shows the consumable summary; the full per-finding list is always written toanalyzer-report.txt. The stale "re-run with --verbose" hint is gone.analyzer-report.txtis detail-only — the summary is no longer duplicated into it.analyzer-summary.txtholds the digest and points to the detail file.analyzer-report.txton warning-only runs too (previously only on errors); covered by a new test.analyze(Path, boolean skipEfx)is now package-private; the public entry point remainsanalyze(Path).JSON output
JsonReportRenderer— renders anAnalysisResultsas a JSON string: asummary(counts, plus per-section counts) and a flat, self-describingfindingsarray (section, severity, rule, problem, subject, referenced assets, message). Intended for programmatic consumers such as the Metadata Manager, which will display the findings in a table so a user can review the analysis before exporting an SDK. No CLI or default-run change — consumers call the renderer directly, exactly like the text renderers.195 tests pass.