Fix for BatchResponseContent.GetResponseByIdAsync nullref and incorrect content header for non json response #369
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
baywet
approved these changes
Feb 16, 2022
Merged
andrueastman
pushed a commit
that referenced
this pull request
Feb 23, 2022
…Bugs Fix for BatchResponseContent.GetResponseByIdAsync nullref and incorrect content header for non json response
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.
This PR closes #368 and closes #22
Changes include:
defaultin the event the HttpResponseMessage message is non existent when trying to deserialize a payload from batchMicrosoft Reviewers: Open in CodeFlow