-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request header should be set instead of add #46899
Comments
This was referenced Oct 30, 2024
github-merge-queue bot
pushed a commit
to microsoft/typespec
that referenced
this issue
Oct 31, 2024
- Remove unused `ClientPipelineApi.CreateMessage` - Add `HttpRequestOptionsApi` to `ClientPipelineApi.Send(Async)` - Replace `HttpMessageApi.ResponseClassifier` with `HttpMessageApi.ApplyResponseClassifier` - Make abstraction more generic This fix is needed for below issues of Azure plugin: Azure/azure-sdk-for-net#46899 Azure/azure-sdk-for-net#46900 Azure/azure-sdk-for-net#46901 Azure/azure-sdk-for-net#46902
The current behavior in Azure client is Add, will keep the behavior unchanged as Add. |
swatkatz
pushed a commit
to swatkatz/typespec
that referenced
this issue
Nov 5, 2024
- Remove unused `ClientPipelineApi.CreateMessage` - Add `HttpRequestOptionsApi` to `ClientPipelineApi.Send(Async)` - Replace `HttpMessageApi.ResponseClassifier` with `HttpMessageApi.ApplyResponseClassifier` - Make abstraction more generic This fix is needed for below issues of Azure plugin: Azure/azure-sdk-for-net#46899 Azure/azure-sdk-for-net#46900 Azure/azure-sdk-for-net#46901 Azure/azure-sdk-for-net#46902
To be consistent with MGC, we decided to use |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
request header should be set instead of add
The text was updated successfully, but these errors were encountered: