Fix URI parameters decoding #18
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
|
Seems like I am facing the same issue. Thanks. |
|
i will re test this case and merge in next week |
|
ok thank you |
|
@ddo Did you have a look on my pull request? Thanks |
|
thank you! and i will bump the version to 1.0.0 soon(follow the semver) after recheck the whole lib |
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.
I slightly changed the deParam function to allow having encoded
&characters in the URI params value.Before this fix, with
foo=bar%26barthedeParammethod returned{foo: "bar", bar: undefined}but now it returns{foo: "bar&bar"}.