Compare json object values instead of byte streams when matching bodies that are content-type json#8860
Merged
Compare json object values instead of byte streams when matching bodies that are content-type json#8860
json#8860Conversation
ArcturusZhang
approved these changes
Aug 21, 2024
scbedd
commented
Aug 21, 2024
JoshLove-msft
approved these changes
Aug 21, 2024
Member
Author
|
Located a hole in the logic where we don't properly handle when the body doesn't parse even when it's marked as This test in java turned it up. Newest commit protects against the unexpected exception + resolves the test invocation locally. |
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.
Resolves #3171