-
Notifications
You must be signed in to change notification settings - Fork 962
[Firebase AI] Add thought summary and signature support #9192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 3f62f8a The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
cc: @dlarocque |
export function getText(response: GenerateContentResponse): string { | ||
export function getText( | ||
response: GenerateContentResponse, | ||
isThought: boolean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe instead of passing a specific boolean for thoughts we pass through a filter function here:
partFilter: () => boolean
and then when we call it in addHelpers()
above it's like getText(response, (part) => !part.thought)
for text()
and it's getText(response, (part) => part.thought)
for thoughtSummary()
. And then in the condition below it's if (part.text && partFilter(part))
This makes it read clearly when it's called (or we can just add a comment before true and false). It might get unwieldy if we have other kinds of text parts in the future that have more complex logic though.
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected Products
Test Logs |
WIP - Added support for including thought summaries and thought signatures.
Manually tested through the quickstart but still needs unit tests and deciding if the approach in
getText
makes sense. Chat handling will also need to be implemented.