Evaluation UI: UX Inconsistency
A pull request for this has already been merged.
- #118 by @Ayush8923 — merged
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by tracing the CSV upload flow and the evaluation results UI to find where the column names are defined. Review the linked pull request and confirm which naming choice was implemented; done means the upload schema and results display use clear, consistent names for question, ground truth, and generated answer.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
When uploading a new dataset, users provide a CSV with question and answer columns. These become the golden dataset's question and
ground truth.
However, in evaluation results, we display columns: question, answer, and ground_truth — where answer is now the
generated response while question and ground_truth are from the original upload. This naming inconsistency creates confusion from a UX
perspective.
Describe the solution you'd like
- Rename the CSV upload columns to question and ground_truth (instead of question and answer)
- This aligns the upload schema with the evaluation results display
- Consistent naming: question = input, ground_truth = expected answer, answer = generated response
Alternative
Keep upload columns as-is but rename ground_truth column in evaluation results UI to expected_answer to differentiate it more clearly
from answer (generated response).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 4
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.
More from ProjectTech4DevAI/kaapi-frontend
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ProjectTech4DevAI/kaapi-frontend#266 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ProjectTech4DevAI/kaapi-frontend#258 · 3 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in ProjectTech4DevAI/kaapi-frontend
Similar issues
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Plugin stuck at "loading" on DSH 0.1.6-alpha.2 — turnTail list slot registration missing options.id Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chrisparsons83/flexspotff#153 ·