fix: wrap evaluator request fields in data object #117
Conversation
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
sergioestebance
force-pushed
the
fix/curl-data-wrapper
branch
2 times, most recently
from
a772667 to
3930121
Compare
The OpenAPI schema generator was missing the `data` wrapper that the
actual API expects for evaluator endpoints.
Before: `{"input": "...", "output": "...", "settings": {...}}`
After: `{"data": {"input": "...", "output": "..."}, "settings": {...}}`
Co-Authored-By: Claude Opus 4.5 <[email protected]>
sergioestebance
force-pushed
the
fix/curl-data-wrapper
branch
from
3930121 to
f3ccd92
Compare
Co-Authored-By: Claude Opus 4.5 <[email protected]>
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
Fix OpenAPI schema generation to correctly structure evaluator request bodies.
Problem
The API documentation showed incorrect request body structure:
{"input": "...", "output": "...", "settings": {...}}But the actual API expects:
{ "trace_id": "optional", "name": "optional", "data": {"input": "...", "output": "..."}, "settings": {...}, "as_guardrail": false }Changes
generateRequestSchema()inscripts/generate-openapi-evals.tsto:input,output, etc.) indataobjecttrace_id,name,as_guardraildataas requiredNote
After merging, run
npx tsx scripts/generate-openapi-evals.tsto regenerateapi-reference/openapi-evals.json.🤖 Generated with Claude Code