ProjectTech4DevAI / ProjectTech4DevAI/kaapi-frontend

Evals UI: Fix inconsistent terminology

Open
#57 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
10h 40m
Merged PRs (30d)
4

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
typescript
Domain
content, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.