[JS] feat: support for v2 Assistants #2193
Merged
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
corinagum
requested review from
a team,
aacebo,
lilyydu,
singhk97 and
rajan-chari
as code owners
lilyydu
reviewed
Dec 2, 2024
added 16 commits
December 3, 2024 10:59
…sages weren't being correctly filtered
corinagum
force-pushed
the
cg/AssistantsPlanner
branch
from
b62c292 to
9fc336e
Compare
lilyydu
approved these changes
Dec 3, 2024
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.
Linked issues
closes: #1585
Details
Please note
This code updates to use v2 assistants, but file search, vector store, and code interpreter handling have not been implemented yet. This work was mainly to remove the dependency
@azure/openai-assistants.Change details
@azure/openai-assistantspackage and useopenaiinAssistantsPlanner.tsAssistantsPlanner.tsto use assistants v2Attestation Checklist
My code follows the style guidelines of this project
I have checked for/fixed spelling, linting, and other errors
I have commented my code for clarity
I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient)
My changes generate no new warnings
I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:
New and existing unit tests pass locally with my changes
Additional information