Conversation
…ment, schema sync, custom assertion discovery - FileType: add 'cases' type; directory scanner only picks up *.eval.yaml - file-type.ts: YAML array root → 'cases'; require .eval.yaml suffix for eval inference - cases-validator.ts: new validateCasesFile() validates YAML array test case files - eval-validator.ts: sync KNOWN_*_FIELDS with yaml-parser.ts (add preprocessors, category, rubrics); add DEPRECATED maps with migration hints for evaluator/assert/eval_cases/expected_outcome; discover custom assertion types from .agentv/assertions/ to suppress false-positive warnings; remove redundant 'note' field - eval-file.schema.ts: remove 'note' field from Zod schema - examples: rename tool-eval-demo.yaml → .eval.yaml; fix trace-file-demo (description → YAML comments); fix basic-jsonl (remove deprecated evaluator); fix prompt-template-sdk (reference_answer → expected_output) - agentv validate examples/: 68/68 valid, 0 warnings Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Deploying agentv with
|
| Latest commit: |
333c7cc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c5cca464.agentv.pages.dev |
| Branch Preview URL: | https://fix-validate-cases-and-examp.agentv.pages.dev |
…n discovery - Validate all files concurrently with Promise.all instead of sequential loop - Cache discoverCustomAssertionTypes() results by directory so N files in the same directory only pay for one filesystem walk (not N) Co-Authored-By: Claude Sonnet 4.6 <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
'cases'type and validated by a newvalidateCasesFile()— each item must haveidandinput.eval.yamlenforcement: directory scanning only picks up*.eval.yamlfiles (not all YAML);inferFileTypeFromPathrequires.eval.yamlsuffix to return'eval', otherwise'unknown'preprocessors,categorytoKNOWN_TOP_LEVEL_FIELDS; addedrubricstoKNOWN_TEST_FIELDS; removed non-existentnotefield from schemaevaluator,assert,eval_cases/evalcases,expected_outcomenow emit specific deprecation messages instead of generic "unknown field" warnings.agentv/assertions/directories (same as runtime) to suppress false-positive "unknown assertion type" warnings for plugin assertion typestool-eval-demo.yaml→.eval.yaml; replaceddescription:with YAML comments in trace-file-demo; removed deprecatedevaluator:from basic-jsonl; replacedreference_answer:with properexpected_output:in prompt-template-sdkagentv validate examples/now reports 68/68 valid, 0 invalid, 0 warningsTest plan
agentv validate examples/→ 68/68 valid, 0 invalid, 0 warningsword-countin sdk-custom-assertion example no longer triggers a false-positive warning🤖 Generated with Claude Code