Added uri_query_json() function #13
Open
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
|
@petere, any chance of merging this? I've created a (slightly different / simpler) implementation for my purposes, but this looks more complete. |
|
@lacanoid I'd suggest working with |
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.
Added uri_query_json() function, to make individual uri query parameters conveniently accessible using json.
This is somewhat clumsy otherwise. JSON is natural for this and also allows for repeating keys.
Uriparser already provides a function for decomposing and decoding a query.
The rest is inspired by hstore_to_json() from hstore.c. Could use another look, to see if everything is ok.
Extension version updated to 1.1. Tests added.