fix: update uri to omit deployment ids for assistant and thread paths #431
+19
−2
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.
Summary:
Solves Assistants Support for Azure's new API version 2024-02-15-preview #430
Tested in my own local application and the URI with the deployment id omitted unblocks the whole process from creating an assistant, thread, and message.
Solution:
Support assistants API by removing the deployment id for certain paths
Example:
https://custom-domain.openai.azure.com/openai/deployments/gpt-35-turbo/assistants
to
https://custom-domain.openai.azure.com/openai/assistants
All Submissions: