Carry JSON Schema type for optional tool fields - #8248
Open
Ege (ege-arhan) wants to merge 1 commit into
Open
Ege (ege-arhan) wants to merge 1 commit into
Ege (ege-arhan) wants to merge 1 commit into
Conversation
Author
|
@microsoft-github-policy-service agree |
This branch has not been deployed
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.
Ran into this while looking at #6848 — optional tool args like country: Optional[str] = None come out of BaseTool.schema without a top-level type, just anyOf. Some providers (Gemini in that report) reject the declaration because a property has no type field.
This just copies the non-null branch's type up when there's exactly one, so anyOf stays untouched and everything else renders the same as before.
Checked test_tools.py locally, 39 passed.