Feat: Structured Outputs for function calling #226
Closed
Conversation
This file contains 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.
What
Support the optional
strictparameter in function definitions, which was released with Structured Outputs.When
strictis provided, the API requiresadditionalPropertiesto be provided in theparametersobject of the function definition as well.The earliest models that support this feature are
gpt-4o-2024-08-06andgpt-4o-mini-2024-07-18.This does NOT include support for the
json_schemaresponse_format for Structured Outputs outside of function definitions.Why
This parameter improves the model's adherence to JSON schemas during function calls. See more
Affected Areas
Non-breaking change to decoder, since only optional parameters were added.