[OpenAI] Edit Customization Layer with Main Typespec#28533
Merged
minhanh-phan merged 20 commits intoMar 19, 2024
Conversation
… openai/update-customizations
… openai/update-customizations
Collaborator
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
deyaaeldeen
reviewed
Mar 18, 2024
minhanh-phan
requested review from
bterlson,
glharper,
jeremymeng,
mpodwysocki,
witemple-msft and
xirzec
as code owners
deyaaeldeen
approved these changes
Mar 19, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Packages impacted by this PR
@azure/openai
Issues associated with this PR
Describe the problem that is addressed by this PR
This PR updates AOAI package to the latest customization tool v2 with the new folder structure. "sources" folder is removed and the generated code will be located in "generated" folder. The PR does not use the latest TypeSpec commit; that will be addressed in a later PR to avoid massive changes to the API.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists