fix(@ai-sdk/google): Make title field optional in grounding metadata schema #9867
+41
−2
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
samjbobb
force-pushed
the
fix/google-retrieved-context-type
branch
from
e55db5e to
9f4d8c1
Compare
samjbobb
force-pushed
the
fix/google-retrieved-context-type
branch
from
9f4d8c1 to
01520c4
Compare
1 task
gr2m
approved these changes
Oct 29, 2025
Collaborator
gr2m
left a comment
gr2m
left a comment
There was a problem hiding this comment.
Great bug report and pull request, thank you Sam! Congratulations to your first contribution to the AI SDK 💐
vercel-ai-sdk bot
pushed a commit
that referenced
this pull request
Oct 29, 2025
…schema (#9867) ## Background A small percentage of the time when using the Gemini "URL Context" feature we get a Zod validation error on the response due to a missing title property. ## Summary Added `.nullish()` to `groundingChunks[].web.title` and `groundingChunks[].retrievedContext.title`. Notes: * I've personally observed the missing `title` property only on `groundingChunks[].web.title`. I'm guessing that the same situation could occur on `groundingChunks[].retrievedContext.title` and they should have the same schema. * I used `.nullish()` instead of `.optional()` to maintain consistency with the rest of `packages/google/src/google-generative-ai-language-model.ts`, though I have only observed a missing (`undefined`) `title` property, not a `title: null`. ## Related Issues Fixes #9842
Contributor
|
✅ Backport PR created: #9893 |
Contributor
Author
|
@gr2m Thank you for your quick responses Gregor! |
vercel-ai-sdk bot
added a commit
that referenced
this pull request
Nov 4, 2025
… metadata schema (#9893) This is an automated backport of #9867 to the release-v5.0 branch. Co-authored-by: Sam Bobb <[email protected]> Co-authored-by: Gregor Martynus <[email protected]>
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.
Background
A small percentage of the time when using the Gemini "URL Context" feature we get a Zod validation error on the response due to a missing title property.
Summary
Added
.nullish()togroundingChunks[].web.titleandgroundingChunks[].retrievedContext.title.Notes:
titleproperty only ongroundingChunks[].web.title. I'm guessing that the same situation could occur ongroundingChunks[].retrievedContext.titleand they should have the same schema..nullish()instead of.optional()to maintain consistency with the rest ofpackages/google/src/google-generative-ai-language-model.ts, though I have only observed a missing (undefined)titleproperty, not atitle: null.Open to feedback on either of those choices.
No documentation updates made. Let me know if needed.
Manual Verification
Added tests.
Checklist
pnpm changesetin the project root)Future Work
N/A
Related Issues
Fixes #9842