Repository navigation
feat: Support multimodal function responses - #181
Merged
Merged
Conversation
Add the FunctionResponse fields from the API reference: - parts: ordered FunctionResponsePart items with inline media, so a function can return images or documents to the model - willContinue and scheduling for NON_BLOCKING function calls Existing function responses are serialized exactly as before. Refs #163
The $ref form needs a matching display name, which FunctionResponseBlob doesn't have, so the API rejects that payload.
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
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.
Refs #163
Adds the
FunctionResponsefields from the API reference, so a function can return images or documents to the model:Changes
FunctionResponse::$parts: orderedFunctionResponsePartitems with inline media. The existingBlobclass is reused for the inline data.FunctionResponse::$willContinueandFunctionResponse::$scheduling(FunctionResponseScheduling) forNON_BLOCKINGfunction calls.Backward compatibility
name,response,id); the new keys are only added when set.schedulingvalue resolves tonull.Tests
toArray()without the new fields (unchanged payload) and with themfrom()with all fields, without optional fields and with an unknownschedulingvaluePartround trip with a multimodal function response