File-based routing setup leads to missed matches #4836
Unanswered
shmuel-levinson-z
asked this question in
Q&A
Replies: 1 comment 4 replies
-
can you please provide a complete minimal example by forking one of the existing stackblitz router examples? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,

I'm working on breadcrumbs for a large app. I'm using file based routing, here is the part of the tree that is of interest
When i navigate to
...settings/all-accounts
the All Accounts component is rendered as expected (it is defined in the lowerindex.tsx
file.However when I navigate to
...settings/all-accounts/edit/user123
the component in$id/index.lazy.tsx
is rendered as expected but the matches only includesettings/all-users/edit/user123/
. I would expect thesettings/all-users/
to also be in the matches. How can I achieve this without changing the index.tsx / index.lazy.tsx combination?Seems to me like the all-users route is being skipped for no good reason. Help would be appreciated!
PS. Logically there is no 'Outlet' in all-users here. The all-users is a completely standalone component and each user page is rendered in the same outlet as the all-users.
Beta Was this translation helpful? Give feedback.
All reactions