Next.js 14 Tutorial - 29 - Unmatched Routes

preview_player
Показать описание

📱 Follow Codevolution

Unmatched Routes
Рекомендации по теме
Комментарии
Автор

I have a problem where the parallel routes don't appear in the browser until I restart the local server

AbdelrhmanShibl
Автор

Maybe this is covered in the next section, but this whole thing seems to fall apart if you try to do multiple subnavigations. I tried to do the same thing for the users slot that you had us do for the notifications slot, but when you navigate back to the default view for either one it will reset the other back to the root slot view as well instead of leaving it unaffected.

TennSeven
Автор

very informative and easy to understand

danieljing
Автор

I really like your teaching and now I am willing to expect your express.js courses bro

KhineMinHtun-jo
Автор

Are both necessary? Page.tsx and default.tsx or can I just remove the page.tsx?

MrUNhelp
Автор

Is it not inefficient? Creating two files with same code.

shivagurung
Автор

absolutely great course. thank you so much!

alihosseinkhani
Автор

in the default.tsx, can i export page from './page' as default or is it necessary to copy everything from page.tsx and put it in default.tsx?

ShivShankar
Автор

so, if you have ten slots, it means you should create default.tsx on every slots?

muhamadizranovan
Автор

This slots feature is great, however I have a question, is it possible to import the component from the page.tsx file to render it in the default.tsx? thanks a lot for these series, it's an amazing content.

SimonGonzalez-tc
Автор

Huh. Slots seemed kinda useful until this point. Now I have to add ANOTHER file (default.tsx) to every goddamn page where you basically have to copy-paste your content. Ridiculous. What happened to DRY?

loveboat
Автор

What about 2 slots with routes? And you navigate both. How to deal with it?

RuslanMahats
Автор

Actually I found an issue in this section. I created the default.tsx and arranged files exactly like this in the video, then I added a not-found.tsx at /app/ folder as the root handler, then refresh the page, and it will show the not-found page instead.

yw
Автор

When will you add videos to React Native playlist?

rahularora
Автор

Why wouldn't I want to render a route that shouldn't be parallel rendered, if I have declared it as parallel route?
Parallel routes are a very powerful structure, and I am sure that the Next engine has a way to determine when these routes have been declared as such. So, the matching of these components with the routes should be different. E.g. "/complex-dashboard" matches with three slots, regardless of what comes next. How come that's not relevant to the component-route matching system?

kikevanegazz
Автор

Hey Codeevolution, I have the same Directory structure with the same pages (i.e., page.jsx) as well as the same code, however I'm getting a blank white page when I route from "/complex-dashboard/archived" to "/complex-dashboard" after clicking on the <Link />. Can you tell me why?

sharpesthawk
Автор

@codevolution What happens if 2 slots have configuration. how are router handled then?

KamalSingh-zool
Автор

First viewer,
Link me up man as entry level react typescript engineer

hayatudeenyusuf
Автор

your course is amazing but i wish if u make a project to apply these concepts cz it's too much and u can do what u want in multiple ways..

worldoflanguages
Автор

This left me confused. From what I can find default.tsx has no particular semantic meaning - it's just some filename. Why does it imply "use this instead"?

warberg