.Net: OpenAI V2 Optional Settings #7409
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
markwallace-microsoft
added
.NET
westey-m
reviewed
Jul 23, 2024
dotnet/src/IntegrationTestsV2/Connectors/AzureOpenAI/AzureOpenAITextEmbeddingTests.cs
Outdated
Show resolved
Hide resolved
westey-m
approved these changes
Jul 23, 2024
…tion + Added OpenAIV2 reference to new Demo
dmytrostruk
approved these changes
Jul 23, 2024
RogerBarreto
merged commit ecd3fee
into
microsoft:feature-connectors-openai
8 of 10 checks passed
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.
Resolve #7111
Optional Settings
As part of this update all the previous enforeced/default settings from OpenAI and AzureOpenAI connectors are now optional, not sending any non-defined information to the server side API, leaving the underlying API to resolve its default value.
Integration Test Fixes
As a small add up to this PR I also added fixes to our Integration Tests when executing against Parallel Function Calling capable models.