-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed as duplicate of#2139
Description
Which project does this relate to?
Router
Describe the bug
When throwing a notFound() error in a dynamic grouped layout, the notFound errors ends up going to the __root route even though you threw it from higher up.
Even though it's the default, I made sure router is in notFoundMode: "fuzzy"
Your Example Website or App
Steps to Reproduce the Bug or Issue
- Go to something like
/aaain the url. - Observe behavior (shows
This should not showcoming from __root`)
Expected behavior
I expected that, when throwing a notFound in a certain route.tsx, that route's notFoundComponent would render. Or, at least, the route below (dynamic route $organizationSlug in that case), if it does not make sense to throw in a grouped layout.
Screenshots or Videos
No response
Platform
- Router / Start Version: 1.132.47
- OS: Windows
- Browser: Chrome & Firefox
- Browser Version: Does not matter
- Bundler: Vite
- Bundler Version: 7.1.7
Additional context
No response
Metadata
Metadata
Assignees
Labels
No labels