Add 'items' field to JSON schema for Gemini compatibility #68
Conversation
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
PiotrCzapla
force-pushed
the
fix/array-for-gemini
branch
from
3463f46 to
5abd826
Compare
PiotrCzapla
force-pushed
the
fix/array-for-gemini
branch
from
5abd826 to
060aae7
Compare
Contributor
Author
|
Here is dialog that test the changes with gemini https://share.solve.it.com/d/e69a17d2a98ec1d9f82ea56377d13bf1 |
jph00
changed the title
Collaborator
|
Nice find! :) BTW instead of prefixing 'Fix:', use the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Gemini models assume that
itemsare present for type: 'array'. Adding items: {} fixes the issue.This prevents 400 Bad Request errors during tool registration. Otherwise, using Gemini with tools like
symfiles_packageresults in an error.