Repository navigation
fix(llm): normalize Gemini schema union types - #238
Merged
Merged
Conversation
stippi
approved these changes
Oct 12, 2026
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
typeunions to Gemini-supportedanyOfschemastypevalues and existing schema sanitization behaviorMotivation
Gemini's
Schema.typeaccepts a single scalar enum value, while tool definitions may use standard JSON Schema unions such as:{"type": ["string", "number", "boolean"]}Sending such a declaration can cause request translation to fail before the model receives the request. Expressing the same union with
anyOfis accepted.Validation
cargo test -p llm vertex --lib(14 passed)cargo check -p llm --testscargo clippy -p llm --all-targets --all-features -- -D warningscargo fmt --all -- --checkgit diff --checkstream_function_call_arguments: truebehavior retainedThis PR intentionally does not change streaming function-call argument behavior.