JSONSchema should use schema description when used for function call #432
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
… and field description as expected.
…when used as function
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
Schemaobjects were usinginstance.descriptionbut not the schema within the schema definition json.Did some research and determined that OpenAI ignores
parameters.descriptionin a function call definition. There may be useful instructions in the schema soto_openaj_fnhelper now joins bothdescriptionvalues together for thefndescription.Changes
[List out the changes you've made in this pull request. Be as specific as possible.]
How Tested
[Explain how you tested this pull request. Include any relevant steps or scripts.]
TODOs
[List any outstanding TODOs or known issues that still need to be addressed.]