feat(firebaseai): add responseJsonSchema to GenerationConfig
#17564
+289
−16
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
gspencergoog
changed the title
gspencergoog
changed the title
responseJsonSchema to GenerationConfig
cynthiajoan
reviewed
Jul 30, 2025
cynthiajoan
changed the title
responseJsonSchema to GenerationConfigresponseJsonSchema to GenerationConfig
cynthiajoan
reviewed
Jul 30, 2025
|
Thanks for the PR, would like to check if it has been tested under both vertexAI and googleAI backend. |
cynthiajoan
reviewed
Jul 30, 2025
Yes, I've tested it on both backends. |
… use in GenerationConfig (firebase#17599) Expose ThinkingConfig class so that it can be used in GenerationConfig
The Developer API was missing support for parts, which was already implemented in the Vertex AI API. This change copies the parsing logic from the Vertex AI function to the function in the Developer API. An existing test file, , has been updated to include a test case for parsing parts, ensuring the functionality is working as expected.
…irebase#17607) * [Infra] Move FirebaseAuth imports to implementation files * Add module import
…17503) * add developer api to live * make the whole process going through * feat(firebase_ai): handle unknown parts when parsing content * tweak the content test * remove the extra exception * Make Live API sending tool response for function calling * update bidi model for googleAI in example * fix analyzer and test * more test fixing --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
…ests (firebase#17612) * ci(firestore): add `--ignore-timeouts` flag for cloud firestore e2e tests * chore: set timeout-minutes value to 60 * remove --ignore-timeouts flag * revert change * chore: apply --ignore-timeouts to all iOS e2e tests * chore: apply --ignore-timeouts to android and macos e2e tests * chore: fix macos ci
* chore(release): publish packages - [email protected] - [email protected] - [email protected] - [email protected] - [email protected]+1 - [email protected] * chore: BoM Version 4.1.0
|
Okay, @cynthiajoan I added an example here that uses I also formatted the output a little better in the "chat" of the example, and updated the regular schema example to match. I also bumped the Gemini model versions in the example's main, since they were pretty old, but I'm happy to revert that if you wanted them to stay that way. |
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.
Description
This adds the
responseJsonSchemafield to the GenerationConfig class, which enables more JSON schema features like$defand$refalong with other advanced JSON schema features that Gemini 2.5 supports.See the Gemini docs for more information about what is supported.
Related Issues
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]).This will ensure a smooth and quick review process. Updating the
pubspec.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?