CivicDataLab / CivicDataLab/ParakhAI-frontend
Storing an evaluation or prompt details [discussion needed]
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 9h 18m
- Merged PRs (30d)
- 4
Description
currently all evaluations are stored in the DB (whether there are test cases inside or not)
- Decision on whether cancelled evaluations need to remain on the platform
- Decision on how much of the prompt libraries we should show in preview (automated evals)
- Flow for storing user generated prompts (for the evaluator to reuse their own prompts easily)
Contributor guide
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
No files, tests, or entry points are named in the issue. First resolve whether cancelled evaluations remain, how much automated-evaluation prompt libraries appear in previews, and how user-generated prompts are stored for reuse; done means these decisions are documented as an agreed implementation flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100