Low-confidence findings bypass the inline threshold
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 69/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend-api-design
Research direction
Read src/pipeline/composer.ts around lines 1632 and 1656, then compare the expectations in tests/pipeline-phase5.test.ts:12627 and tests/github-publisher.test.ts:156. Trace how minInlineConfidence is applied to low-confidence verified exceptions and how the publisher handles inline findings. Done means the report, plan, and PR publisher agree on whether the finding is inline or summary-only, with the tests expressing that behavior.
Written by the indexing model from the issue text.
Description
Problem: A low-confidence verified exception returns before minInlineConfidence is checked, so the report and plan mark a finding inline while the PR publisher demotes it to summary-only.
File:line: src/pipeline/composer.ts:1632,1656; src/github/publisher.ts:94.
Evidence: Conflicting expectations in tests/pipeline-phase5.test.ts:12627 and tests/github-publisher.test.ts:156; @architect checked the branch.
Suggested fix size: S.
Found during #44 (workstream C, challenged by @architect).
- 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