Evaluation 2.0: Transition to v2 API

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api, frontend

Research direction

Start by tracing the console’s current v1 paths for dataset upload, run triggering, improve-prompt, and scoring UI. Compare each path with the v2 API contract, then verify the three judge metrics, verdicts, overall summary, duplication override, and prompt-iteration loop in the UI. Done means all listed flows use v2 behavior.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem?
The console currently uses the v1 evaluation API, which lacks the features and speed of v2. The new v2 API offers significant improvements, including a better scoring system and additional functionalities that are not currently represented in the UI.

Describe the solution you'd like

  • Transition dataset upload, run trigger, and improve-prompt to the v2 endpoints
  • Update scoring UI to reflect the three judge metrics, verdicts, and overall summary
  • Introduce v2-specific controls: per-run duplication override and prompt-iteration loop
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

  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.

More from ProjectTech4DevAI/kaapi-frontend

All issues in ProjectTech4DevAI/kaapi-frontend

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.