ProjectTech4DevAI / ProjectTech4DevAI/kaapi-frontend
Evaluation: Add verdict badges for scores
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem?
Each numeric judge-metric score has a traffic-light verdict band, but the UI only displays the raw number. This requires users to remember cutoffs to interpret scores correctly.
Describe the solution you'd like
- Implement a verdict badge component with three bands: Good (4–5), Needs Refinement (2–3), Needs Improvement (0–1)
- Display it alongside each metric score and on the overall run-level verdict
- Exclude badges for cosine scores and unscoreable /
N/Aentries
Original issue
Is your feature request related to a problem?
Each numeric judge-metric score carries a traffic-light verdict band, but the UI shows only the raw number — so a reader has to remember the cutoffs to know whether a 3 is fine.
Describe the solution you'd like
- Add a verdict badge component with the three bands: Good (4–5), Needs Refinement (2–3), Needs Improvement (0–1)
- Render it next to each metric score and on the run-level overall verdict
- Render no badge for cosine scores and unscoreable /
N/Aentries, which carry none
Parent: #265
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the metric-score and run-level verdict rendering entry points, then inspect how cosine and unscoreable or N/A values are represented. Done means the three specified bands appear beside eligible metric scores and the overall verdict, with no badge for excluded entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100