Rendered coverage reports omit planner skip paths and reasons
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 73/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- tooling
Research direction
Start with src/pipeline/review-runner.ts lines 1021–1065 and 1083–1093, then read src/util/coverage-summary.ts lines 26–59 to trace how planner skips reach the rendered report. Use the offline probe mentioned in the issue to check the current output. Done means the rendered report shows each skipped path and its reason instead of only a generic excluded count.
Written by the indexing model from the issue text.
Description
Problem: A planner skip loses its path and reason in the rendered coverage report, which shows only a generic excluded count; the artifact is the only place with path and reason.
File:line: src/pipeline/review-runner.ts:1021-1065,1083-1093; src/util/coverage-summary.ts:26-59.
Evidence: @lead-dev's offline probe; @architect notes the previous claim that skips are listed was wrong and did not rerun the probe. Related existing issue: #31.
Suggested fix size: S.
Found during #44 (workstream A, challenged by @lead-dev).
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 1
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from 0xPolygon/codegenie
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
All issues in 0xPolygon/codegenie
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day