fix(schema): stringify non-string enum values in Google tool format#610
Closed
mhsdef wants to merge 1 commit intoagentjido:mainfrom
Closed
fix(schema): stringify non-string enum values in Google tool format#610mhsdef wants to merge 1 commit intoagentjido:mainfrom
mhsdef wants to merge 1 commit intoagentjido:mainfrom
Conversation
Google's Gemini API requires enum values to be strings. When a tool parameter schema contains integer or atom enum values, the API rejects the request. This adds a stringify_enums pass to to_google_format/1 that coerces all enum values to strings before sending. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Hmm, this NimbleOption vs JSON Schema, across providers........is...somethin'. |
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.
Description
Google's Gemini API requires all enum values in tool parameter schemas to be strings. When a schema contains integer or atom enum values (e.g.,
[1, 2, 3]), the API rejects the request. This adds astringify_enums/1pass toto_google_format/1that coerces all enum values to strings before wire encoding.Type of Change
Breaking Changes
N/A
Testing
mix test)mix quality)Checklist
CHANGELOG.md(it is auto-generated by git_ops)Related Issues
N/A