Evals UI: Fix inconsistent terminology
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Search the text evaluation UI for remaining "Upload" and "Results" references, then inspect the tab initialization and the surrounding labels, links, buttons, and guidance text. Done means the listed UI surfaces consistently use "Datasets" and "Evaluations", including the default tab state.
Written by the indexing model from the issue text.
Description
Describe the current behaviour
The text evaluation UI uses inconsistent terminology across different components:
- Tabs and navigation refer to "Upload" and "Results"
- Some button labels and guidance text still use the old naming convention
- Tab initialization defaults to the outdated terminology
This inconsistency exists because terminology was updated from "upload" → "datasets" and "results" → "evaluations" during initial development, but some references were missed in the implementation.
Describe the enhancement you'd like
Update all remaining UI text to use consistent terminology throughout the text evaluation feature.Specific changes needed:
- Rename all instances of "Upload" to "Datasets"
- Rename all instances of "Results" to "Evaluations"
- Update tab labels, navigation targets, and button text
- Update guidance text and helper messages
- Modify default tab initialization to use "Datasets"
This ensures complete naming consistency across:
- Tab headers
- Navigation links
- Button labels
- User guidance text
- Default state initialization
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 19h 4m
- Merged PRs (30d)
- 6
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 ·
-
bug enhancement
ProjectTech4DevAI/kaapi-frontend#286 · 1 assignee ·
All issues in ProjectTech4DevAI/kaapi-frontend
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100