-
-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
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
Root route component is rendered for non-matching-route path but not for missing resource #2255
Comments
Please attach a valid minimal reproduction showing off the issue in question. Edit: Link to a stackblitz starter - https://stackblitz.com/github/tanstack/router/tree/main/examples/react/quickstart-file-based |
I’ve used the Steps to reproduce:
|
Throwing a
Navigating to a route that DOES NOT EXISTS in the route-tree, results in this route-tree.
Note that this configuration does not have a By default the Router has the setting of |
Thanks for the further investigation and writing a test-case @SeanCassiere. I haven’t thought about the My expected behavior would be that the behavior is consistent across all scenarios, so either the |
Which project does this relate to?
Router
Describe the bug
The component defined in the
rootRoute
is rendered when a non-matching path riggers the rendering of thenotFoundComponent
but it is not rendered when a child route trows anotFound()
value in its loader.Your Example Website or App
https://stackblitz.com/edit/github-yk78pg-lfpyxu?file=src%2Fmain.tsx
Steps to Reproduce the Bug or Issue
component
andnotFoundComponent
component
as well as thenotFoundComponent
gets renderedExpected behavior
I would expect the behavior to be the same in both scenarios.
Screenshots or Videos
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: