Support preserving order of parameters when serializing to a Map. #106
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
wuerges
changed the title
wuerges
changed the title
|
Hey, this is exactly what I need! Any chance this will be merged soon? |
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.
Dear samscott89,
Please consider this pull request.
What it does?
This PR adds support for deserializing queries into ordered maps, such as
IndexMap.How?
It adds a new feature, called
indexmap, that replaces theBTreeMapused internall byserd_qswith anIndexMap.Why?
Sometimes the order of the keys in the query is important. On example is sorting. What if you want to sort by one field, and then by other?
Was it tested?
There's a new test. It parses a two queries into a map. The queries are almost the same, but the order of the keys is swapped.