More granular control #19
Open
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
Problem:
You can only specify one regex per entry,
but request and response mostly need different regexes
-> two conflicting values for the same id.
Could be solved with two regexes per entry, one for request, one for
response
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 adds more granular control over where the tokens are retrieved and inserted.
It add the option to extract from a request, as well as a response and different options, whether the token should be applied to the url, cookie, header, ...
Also I converted the files from my tabs to spaces, appearently there were some other files that used tabs instead, that got converted too. I hope this is fine. Now the whole code uses the same convention (I think).