-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stub value substitution using a template #1249
Merged
Merged
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
external example
…to platform-specific path
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.
What:
Introduce two templating features "{{REQUEST.QUERY-PARAMS.enabled}}" and "{{@DaTa}}", in order to coordinate values in example.
Why:
"{{REQUEST.QUERY-PARAMS.enabled}}" <- this allows a value from the request to be expected in the response. This way you won't have to provide multiple examples when the only difference is one value in the request and response, and they are coordinated.
"{{@DaTa}}" <- sometimes value A in the request should go with value B in the response. For example, let's say that when in the request JSON payload the value of
department
isengineering
, the value of thelocation
in the response JSON payload should beBangalore
, and the currency should beRupees
. This feature enables this coordination to be done in a single example file.Checklist: