Add substitute capability #20
Closed
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
* updated the README * added tests To preserve backwards compatibility with existing filenames, I preserved “headerNames” in the hashparts array instead of renaming it to “headers” as would otherwise make sense.
Closed
|
Closed in favor of #22, which moves this PR to a different branch. |
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.
Hi @avik-das - I added the substitution capability suggested in #13.
Now you can do:
And the fixtures will contain , while the requests will contain the value of MY_ACCESS_TOKEN.
I added tests, but couldn't quite figure out how to test the fixture files themselves. I did check that they look right, though.