matchRoute matches pending location
Hey, I have a small helper utility for matchRoute and I run into some issues with it returning in a in-between state.
For the setup:
- I have a redirect in my beforeLoad that is async that always redirects towards
- My link navigates to
- My component consumes
I kind of expected the navigation event to keep the old router state for the component tree until the loaders (including beforeLoad) are resolved and then swap it over but it seems that there is a in-between state where the click on the Link leads to the route not being matched for a split-second.
There is a screenshot attached of the router states and what is being matched attached.
I'm not sure if this is a misunderstanding on my part, but it feels "off" because the pattern of components being useable on sections of routes seems sensible and it not being compatible with redirects in async
For the setup:
- I have a redirect in my beforeLoad that is async that always redirects towards
$organizationId/$projectId- My link navigates to
$organizationId- My component consumes
matchRoute("$organizationId/$projectId")I kind of expected the navigation event to keep the old router state for the component tree until the loaders (including beforeLoad) are resolved and then swap it over but it seems that there is a in-between state where the click on the Link leads to the route not being matched for a split-second.
There is a screenshot attached of the router states and what is being matched attached.
pendingstate.locationstate.pendingMatchesstate.matchesI'm not sure if this is a misunderstanding on my part, but it feels "off" because the pattern of components being useable on sections of routes seems sensible and it not being compatible with redirects in async
beforeLoad
