Closed
Conversation
|
👍 This would be very helpful! |
|
This is awesome. It would be great to do the same thing for the path also,
|
Owner
|
See: #77 (comment) |
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
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.
Request bodies are most often encoded as
application/json,application/x-www-form-urlencoded, orapplication/xml. Each of those encodings can represent the same data in more than one way.For example, in JSON encoding,
{"a":1, "b":2}is equivalent to{"b":2, "a":1}. In fact, some JSON serializers behave nondeterministically as to which of those two they emit.Therefore, it usually doesn't make sense to test the body of a request using
-[NSData equals]. Instead, you want to use a notion of equality appropriate to the encoding.This pull enables matching a request body using an arbitrary block, like so: