-
Notifications
You must be signed in to change notification settings - Fork 0
Support nested output schemas in reference validation #401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
zhongkaifu
wants to merge
10
commits into
main
Choose a base branch
from
codex/update-reference-check-for-nested-params
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
2a0e93c
Support nested out param schemas
zhongkaifu 314887a
Accept max_repair_rounds in planner
zhongkaifu cbdf18c
Avoid max_repair_rounds limiting analysis
zhongkaifu 0be3845
Remove max_repair_rounds parameter
zhongkaifu dabfba1
Remove fixed temperature for check_workflow
zhongkaifu 03e89c1
Handle dataclass validation errors in logs
zhongkaifu f12312b
Document nested out_params_schema shorthand
zhongkaifu edfb7da
Fix log_warn usage in orchestrator
zhongkaifu 798ccba
Enforce loop body action node in check_workflow
zhongkaifu 43021d4
Validate condition branch targets
zhongkaifu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new
_coerce_out_param_schematreats any mapping that lackstype/properties/$schemaas a nested object map, which changes the previous behavior for field-level schemas that only use other JSON Schema keywords (e.g.,{"enum": [...]},{"oneOf": [...]},{"items": {...}}). Those were previously passed through as-is, but now get coerced into{type: object, properties: {enum: ...}}, so reference validation will interpretfoo.enumas a property instead of applying the schema tofoo. This breaks existingout_params_schemadefinitions that rely on keyword-only schemas; consider broadening the “already a schema” check to include other JSON Schema keywords.Useful? React with 👍 / 👎.