Issue with Nested Parallel Routes and Conflicting Routes
Unanswered
Amruth Pillai posted this in #help-forum
Hello!
I hope to explain my issue as clear as possible as it's a bit specific, but I'm sure it's something others have faced before.
I have this sort of routing setup using parallel routes where I try to display a page as a modal on click. A similar /work-order/[id] page also exists. The Parallel Routing mechanism seems to be working just fine.
The issue occurs when I visit a page like
But because the
I hope to explain my issue as clear as possible as it's a bit specific, but I'm sure it's something others have faced before.
I have this sort of routing setup using parallel routes where I try to display a page as a modal on click. A similar /work-order/[id] page also exists. The Parallel Routing mechanism seems to be working just fine.
app/[locale]/@peek on main [!?]
❯ tree
.
├── (.)work-order
│ └── [id]
│ └── page.tsx
└── default.tsx
3 directories, 2 filesThe issue occurs when I visit a page like
/work-order/overview which is not part of the [id] route, but there exists an actual page under the overview folder.But because the
[id] intercept takes priority, it goes to this route and thus fails. How do I ensure I don't intercept specific routes when working with Parallel Routes?6 Replies
Taking https://nextgram.vercel.app/photos/1 as an example, I basically need a route at https://nextgram.vercel.app/photos/overview which shouldn't be intercepted and should display the default page.
Please, could someone help 🙂
@ᴉuɐpɹɐɐ I see. But I checked the docs for intercepting routes on Next.js as well and there was no explanation on how to skip certain routes from being intercepted. I checked the Discord too, nothing on it.
oh its both intercepting routes and parallel routes
my bad