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
Problem: nested routes work as expected when a basepath is set to the Router and navigation is done from a root Route.
However, if I trigger a full page reload and try to let the Router pick up a nested Route from the current URL, then no Route content is displayed and the Router doesn't fall back to any other Route in the expected fallback order.
<Router basepath="/host">
<Link to="svelte">Go to Svelte</Link>
<Link to="test/1234">Go to test with id 1234</Link>
<Route path="svelte">Yeah, Svelte!</Route>
<Route path="test/:id" let:params>at: {params.id}</Route>
<Route>404</Route>
</Router>
Expected content after full page reload:
Actual content after page reload:
Tested version: 3.2.2
The text was updated successfully, but these errors were encountered:
Problem: nested routes work as expected when a basepath is set to the Router and navigation is done from a root Route.
However, if I trigger a full page reload and try to let the Router pick up a nested Route from the current URL, then no Route content is displayed and the Router doesn't fall back to any other Route in the expected fallback order.
Expected content after full page reload:
Actual content after page reload:
Tested version: 3.2.2
The text was updated successfully, but these errors were encountered: