Skip to content

Conversation

@xek
Copy link
Contributor

@xek xek commented Oct 6, 2025

No description provided.

@xek xek changed the title fix(google): handle const in tool schemas for Gemini (string=>enum; drop non-string const)\n\n- Rewrite string const to enum [value]\n- Drop non-string const to avoid Gemini API 400s\n\n test(google): add unit tests for const handling fix(google): handle const in tool schemas for Gemini (string=>enum; drop non-string const) Oct 6, 2025
…rop non-string const)

- Rewrite string const to enum [value]
- Drop non-string const to avoid Gemini API 400s
- test(google): add unit tests for const handling

Closes evalstate#420
@xek xek force-pushed the fix/google-const-schema branch from 0122a09 to b32e1be Compare October 6, 2025 10:07
@evalstate
Copy link
Owner

Thanks very much 👍. Added an e2e test as i was curious what other providers did with this (they are all fine :) )

@evalstate evalstate merged commit 6f767d0 into evalstate:main Oct 6, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants