Handle query parameters, including them in render data. #68
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
Query strings on request URIs are parsed and provided to templates and executables as render data at `request.query-parameters`. This value will typically be a map of key/value pairs. This commit also backwards-incompatibly relocates the request route's placement in render data from the top-level `request-route` property to `request.route`.
|
This pull request contributes to #12. |
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.
Query strings on request URIs are parsed and provided to templates and executables as render data at
request.query-parameters. This value will typically be a map of key/value pairs.This commit also backwards-incompatibly relocates the request route's placement in render data from the top-level
request-routeproperty torequest.route.