feat(eval): load explicit TypeScript eval configs#1690
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
0c0e375
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://be998c49.agentv.pages.dev |
| Branch Preview URL: | https://feat-av-kfik-47-eval-config.agentv.pages.dev |
391d237 to
0c0e375
Compare
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
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
AgentV can now run and validate explicit TypeScript eval configs without treating every
.tsfile as runnable eval authoring. The supported CLI/programmatic contract is a default-exportedEvalConfigfrom*.eval.tsor*.eval.mts; Promptfoopromptfooconfig.ts,agentvconfig.ts, generic config files, and.agentv/assertions/*.tsremain outside eval config loading.This also tightens the published SDK authoring surface around one public
EvalConfigtype.defineEval(config)remains only as a thin optional helper, whileEvalDefinitionandevalSuite()are removed from the SDK TypeScript eval authoring exports and docs.Design Notes
packages/core, and CLI eval/validate paths route through that shared loader.*.eval.tsand*.eval.mts, while broad globs and directory scans filter arbitrary TypeScript helpers.agentv validatenow materializes TypeScript eval configs through the core loader so parse/export/contract errors match eval execution behavior.Validation
bun --filter @agentv/core buildbun --filter @agentv/sdk buildbun test apps/cli/test/commands/validate/validate-files.test.ts apps/cli/test/commands/eval/shared.test.ts apps/cli/test/commands/eval/discover.test.ts packages/core/test/evaluation/loaders/ts-eval-loader.test.ts packages/sdk/test/eval-authoring.test.ts packages/sdk/test/grader-helpers.test.ts packages/sdk/test/package-graph.test.tsbun apps/cli/src/cli.ts validate examples/features/sdk-eval-authoring/evals/greeting.eval.tsbun apps/cli/src/cli.ts eval examples/features/sdk-eval-authoring/evals/greeting.eval.tsRed/green UAT: on the pre-branch
maincheckout,agentv validate /tmp/.../red.eval.tsreportedTotal files: 0; on this branch, the same direct*.eval.tsshape validates as one valid file.Live dogfood:
bun apps/cli/src/cli.ts eval /tmp/agentv-ts-eval-dogfood-*/live.eval.ts --targets /tmp/agentv-ts-eval-dogfood-*/targets-gemini.yaml --target live-gemini --grader-target live-gemini-grader --workers 1 --threshold 0.8passed 1/1 with a live Gemini target and real Geminillm-rubricgrader.Evidence
Private evidence branch:
EntityProcess/agentv-private:evidence/av-kfik-47-eval-config-tsat commit525dc45.Related: av-kfik.47