Description
User story
Reporting uncovered lines/branches/functions as individual issues in the coverage plugin isn't very consumer-friendly (too verbose) and has a big impact on data storage size. A more compact and understandable output format would be welcome. A table would be an option for coverage, although an expandable file tree would be even more convenient. This tree format would be applicable to some Lighthouse audit outputs as well.
Design - PoC
See Markdown formatting options here.
Implementation plan
- Define tree audit details Zod schema in CLI #994
- code-pushup/portal#596
- Support tree audit details in upload command #996
- Format tree audit details in Markdown #997
- code-pushup/portal#597
- Convert code coverage issues to tree #999
- Convert docs coverage issues to tree #1000
- Add tree details to Lighthouse audits #1001