Fix canonical query sort #130
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
The sort for the query is defined as being on the keys and not keys + values. Switch from the custom code to the built in Query().Encode() which does the right thing once passed through a replace of + with %20.
|
This is also fixed in #118 but its a good stand alone fix as there seems to be some reticence to merge the other PR for some reason :( |
|
Closing due to lack of feedback, which has forced us to switch to an alternative implementation |
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.
The sort for the query is defined as being on the keys and not keys + values.
Switch from the custom code to the built in Query().Encode() which does the right thing once passed through a replace of + with %20.