Added support for response code based multi example matching. #797
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.
Overview
Certain tooling like NSwag generates examples for separate response code differently. i.e. Request body contains examples field with multiple response code values as keys and actual example as value. Meanwhile, relative responses will simply define
exampleas actual example value.Here's example definition generated by NSwag.
Since Our existing support (#792) only supports example matching based on examples key-matching, such definitions created collections with multiple examples that users might not find useful.
This PR adds support for collection generation from such definition to have response code based examples matching. More details is mentioned in code. And related tests has also been added.