Fix issue #786 #797
Merged
Fix issue #786 #797
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
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 is addressed to update the function
Utilities.appendQueryStringbehavior. As noted in this issue, this function does not cover duplication query keys after my last changes.Until my previous changes, this function completely overrides all query string and append a new one. I am not sure that it was correct behavior because the function is called
appendQueryStringnotoverrideQueryStringorsetQueryString. My new implementation takes it into account more precisely. So, this function does not override the current query string, instead of function adds a new query to it if missed or updates the existing one.