Refine client pipeline abstraction #5044
Merged
Conversation
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
… into tuple-expression
microsoft-github-policy-service
bot
added
the
emitter:client:csharp
Collaborator
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
ArcturusZhang
approved these changes
Nov 11, 2024
Member
|
looks like we are on a path of "abstraction by procedure" instead of "abstraction by API". |
JoshLove-msft
approved these changes
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
ClientPipelineApi.ProcessMessage(Async)abstract directlyClientPipelineApi.Send(Async), it is covered in above itemHttpMessageApi.ExtractResponse, it is covered in the first itemCorresponding change in Azure plugin: Azure/azure-sdk-for-net#47049