refactor: rename eval_set to dataset across codebase#814
Merged
Conversation
Rename every occurrence of eval_set to dataset — core types, wire format, API endpoints, Studio UI labels, routes, and component names — to align with industry conventions (Braintrust, LangSmith, DeepEval all use "dataset"). Backward compatibility maintained: - JSONL parser/manifest reader accept both eval_set and dataset fields - Zod schema accepts both field names (eval_set as deprecated alias) - Pipeline bench/grade read manifest.dataset ?? manifest.eval_set - Trace stats CLI accepts --group-by eval-set as deprecated alias Studio UI changes: - "Categories" → "Datasets" in headings and labels - Route /runs/:runId/category/:category → /runs/:runId/dataset/:dataset - CategorySidebar → DatasetSidebar component rename - API endpoint /api/runs/:filename/categories → /datasets Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying agentv with
|
| Latest commit: |
b622b3f
|
| Status: | ⚡️ Build in progress... |
Rename "eval_set" to "dataset" in all 42 example baseline JSONL files under examples/features/ and examples/showcase/ so new users see the current field name. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #812
eval_setfield todatasetin core types (EvalTest,EvaluationResult), Zod schema, YAML/JSONL parsers, orchestrator, and OTel exporter/categories→/datasets), pipeline (input/run/bench/grade), trace (show/stats/utils)CategorySummary→DatasetSummary,CategoriesResponse→DatasetsResponse, route/category/→/dataset/, heading "Categories" → "Datasets",CategorySidebar→DatasetSidebareval-schema.jsonandrouteTree.gen.tseval_setanddataset, pipeline readers usedataset ?? eval_set, trace stats accepts--group-by eval-setas deprecated aliasRisk
High — breaking API change (renamed wire format fields, API endpoint, route URLs). Backward compat maintained for reading old data.
Test plan
bun --filter @agentv/core typecheck— cleanbun --filter @agentv/core test+bun --filter agentv test— 353 tests pass, 0 failbun --filter @agentv/studio build— builds cleanbiome check .— lint cleaneval_setfield in Studio🤖 Generated with Claude Code