Pass route params to handlers. #29
Merged
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
Eomm
reviewed
Jul 26, 2019
| @@ -286,3 +286,32 @@ test(`Should return 404 on http request`, t => { | |||
| t.end() | |||
| }) | |||
| }) | |||
|
|
|||
| test('Should pass route params to handlers', t => { | |||
There was a problem hiding this comment.
Could we test also the params empty case?
So we will not have regression in future
There was a problem hiding this comment.
Sounds good, I added a test with empty params.
Eomm
approved these changes
Jul 26, 2019
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
find-my-wayrouter already supports parsing route params.This PR simply passes the extracted route params on into the route handler, so that they can be used and don't have to be parsed again.