Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support all <Route> props in react-router-config
See original GitHub issueRecently the sensitive flag was added, but it seems that it is not possible to set this flag when building routes using react-router-config.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Using react router, how can I pass component props using a ...
In your Update #1 just extract the props you want const routeConfig = [ { path: '/', exact: true, component: () => <HomePage...
Read more >Primary Components - React Router v5
There are two route matching components: Switch and Route . When a <Switch> is rendered, it searches through its children <Route> elements to...
Read more >Support all <Route> props in react-router-config #5803 - GitHub
A good PR might be to simplify things by just passing all the options on the route object to the <Route> as direct...
Read more >How To Handle Routing in React Apps with React Router
In React, routers help create and navigate between the different URLs that make up your web application. They allow your user to move...
Read more >Ultimate React Router v6 Guide
This nesting is pretty simple to do. All you need to do is make a parent Route that has the path prop set...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It looks like
renderRoutesis manually passingstrictandexact, so it needs to be updated to also passsensitive. @jaap3 a PR that makes this change would be appreciated (with a test, please).matchRoutesalready just passes therouteobject tomatchPath, so it doesn’t need any changes.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.