You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 26, 2018. It is now read-only.
The routes define an important aspect of the route namely the params. I've looked around and for this to work the routes need to be passed to the middleware.
Internally the way react-router does this is beyond me atm but I think this is doable. I'll update this issue with my progress and maybe provide a pull request for it.
The reason I think this is important is that the routes already define this structure and the logic for parsing routes in defined in react-router replicating this work (while it's easy to grep some like an ID from an URI) I'd very much prefer if these things were not dependant on each other.
The routes define an important aspect of the route namely the
params
. I've looked around and for this to work the routes need to be passed to the middleware.Internally the way
react-router
does this is beyond me atm but I think this is doable. I'll update this issue with my progress and maybe provide a pull request for it.The reason I think this is important is that the routes already define this structure and the logic for parsing routes in defined in
react-router
replicating this work (while it's easy to grep some like an ID from an URI) I'd very much prefer if these things were not dependant on each other.In essence this is what I want.
The obvious caveat is that this depends on an private react-router API,
matchRoutes
...The text was updated successfully, but these errors were encountered: