[WIP] Add caseSensitive option for query param keys matching #63
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.
Fixes #57.
This is basically what was requested in #57, it adds a setter,
.caseSensitive
. Have a look at the test case. Then when query param keys are being matched, it should take that into account.Right now, only
getQueryParamValue
andgetQueryParamValues
are changed but I believed other places such asdeleteQueryParam
,hasQueryParam
andreplaceQueryParam
should also be changed for consistent behavior.@derek-watson Tell me what you think about this, if you think this method is OK, I'm going to complete this.