We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be useful to have declarative components. Those components:
A component like that would be something similar to this
<RouterProvider> <RouteMatch path="/"> <ChildComponent /> </RouteMatch> <RouteMatch path="/user/:id"> { (req, ctx) => <ChildComponent id={req.params.id} /> } </RouteMatch> </RouterProvider>
Question: should the children receive the req, ctx tuple or simply the parameters?
req, ctx
<RouteMatch path="/user/:id"> { (props) => <ChildComponent id={props.id} /> } </RouteMatch>
A good reference could be the @reach/router Match implementation.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be useful to have declarative components. Those components:
Possible implementation
A component like that would be something similar to this
Question: should the children receive the
req, ctx
tuple or simply the parameters?A good reference could be the @reach/router Match implementation.
The text was updated successfully, but these errors were encountered: