Fix: Multiple Matchers Consuming Request Body Causing Stub Handler Failure #28
Conversation
This file contains 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.
This PR has fixed a bug where the stub handler would fail when there are multiple matchers that use the request body for matching.
This issue occurs particularly in scenarios where the path and method match exactly, and the API type, such as jsonrpc 1, is included within the request body. In cases of stubbing APIs that incorporate the API type or operation kind in the request body, there might be multiple matchers specified that consume the request body.
Footnotes
https://www.jsonrpc.org/specification ↩