Hide the not-yet-implemented file handling APIs #81
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
When the image preparation APIs were added to the server API, the general purpose file preparation APIs were also incorrectly marked as public in the client SDK API. Having those APIs available suggests that adding other file types (text files, PDFs, etc) to the chat context via the SDK is expected to work, when that simply isn't true (yet).
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When the image preparation APIs were added to the server API, the general purpose file preparation APIs were also incorrectly marked as public in the client SDK API.
Having those APIs available suggests that adding other file types (text files, PDFs, etc) to the chat context via the SDK is expected to work, when that simply isn't true (yet).