Nested routes — Ichma-ich route yaratish
TanStack Router'da ichma-ich (nested) routelar: Outlet orqali umumiy layoutlarni saqlash, file-based va code-based yondashuvlar, parallel yuklanish va render optimallashuvi.
14-dars
Nested routes — Ichma-ich route yaratish
Tasavvur qiling, siz planshetingizdagi "Sozlamalar" (Settings) ilovasini ochdingiz. Ekranning chap tomonida doimiy turadigan bo‘limlar ro‘yxati bor: Wi-Fi, Bluetooth, Bildirishnomalar, Xavfsizlik. O‘ng tomonda esa qaysi bo‘limni tanlasangiz, faqat o‘shaning parametrlari almashadi. Har bir yangi bo‘limga o‘tganingizda butun ilova o‘chib-yonmaydi — faqat ichki oyna yangilanadi.
Veb-dasturlashda bu arxitektura Nested Routes (Ichma-ich marshrutlar) deb ataladi. U umumiy boshqaruv panelini (masalan, Sidebar, Header) bitta joyda saqlab, sahifalararo o‘tishda faqat kerakli kontent qismini <Outlet /> orqali almashtirish imkonini beradi.
1. File-based routing'da Nested Routes qanday yasaladi?
File-based routing tizimida ichma-ich marshrut yaratish uchun ota marshrut nomi bilan bir xil papka ochiladi.
Papka va fayllar strukturasi:
src/
└── routes/
├── dashboard.tsx -> 1. Ota Layout fayli (<Outlet /> bilan)
└── dashboard/ -> 2. Dashboard ichidagi bola sahifalar papkasi
├── index.tsx -> URL: "/dashboard" (Asosiy panel)
├── profile.tsx -> URL: "/dashboard/profile" (Profil sahifasi)
└── settings.tsx -> URL: "/dashboard/settings" (Sozlamalar)
[!NOTE]
dashboard.tsxfaylidashboard/papkasi bilan yonma-yon turadi. TanStack Router buni ko‘rganda,dashboard.tsxni ushbu papka ichidagi barcha sahifalar uchun ota layout deb taniydi.
Ota Layout fayli: src/routes/dashboard.tsx
// src/routes/dashboard.tsx
import { createFileRoute, Outlet, Link } from '@tanstack/react-router'
export const Route = createFileRoute('/dashboard')({
component: DashboardLayout,
})
function DashboardLayout() {
return (
<div style={{ display: 'flex', minHeight: '100vh', fontFamily: 'sans-serif' }}>
{/* 1. Doimiy turuvchi yon menyu (Sidebar) */}
<aside style={{ width: '240px', background: '#f8fafc', padding: '1.5rem', borderRight: '1px solid #e2e8f0' }}>
<h2 style={{ fontSize: '1.2rem', marginBottom: '1.5rem' }}>Boshqaruv Paneli</h2>
<nav style={{ display: 'flex', flexDirection: 'column', gap: '0.75rem' }}>
<Link to="/dashboard" activeProps={{ style: { fontWeight: 'bold', color: '#2563eb' } }}>
Asosiy ko'rinish
</Link>
<Link to="/dashboard/profile" activeProps={{ style: { fontWeight: 'bold', color: '#2563eb' } }}>
Mening profilim
</Link>
<Link to="/dashboard/settings" activeProps={{ style: { fontWeight: 'bold', color: '#2563eb' } }}>
Tizim sozlamalari
</Link>
</nav>
</aside>
{/* 2. Bola sahifalar (index, profile, settings) aynan shu Outlet ichida chiziladi */}
<main style={{ flex: 1, padding: '2rem' }}>
<Outlet />
</main>
</div>
)
}
Bola sahifa misoli: src/routes/dashboard/profile.tsx
// src/routes/dashboard/profile.tsx
import { createFileRoute } from '@tanstack/react-router'
export const Route = createFileRoute('/dashboard/profile')({
component: ProfilePage,
})
function ProfilePage() {
return (
<div>
<h1>Foydalanuvchi Profili</h1>
<p>Bu sahifa DashboardLayout ichidagi Outlet orqali ko'rinadi.</p>
</div>
)
}
2. Code-based routing'da Nested Routes qanday yasaladi?
Code-based yondashuvda ierarxiya createRoute, getParentRoute va addChildren metodlari orqali qo‘lda bog‘lanadi:
import { createRootRoute, createRoute, createRouter } from '@tanstack/react-router'
const rootRoute = createRootRoute({ component: RootComponent })
// 1. Dashboard ota route'i (Layout)
const dashboardRoute = createRoute({
getParentRoute: () => rootRoute,
path: 'dashboard',
component: DashboardLayout,
})
// 2. Dashboard ichidagi bola routelar
const dashboardIndexRoute = createRoute({
getParentRoute: () => dashboardRoute,
path: '/',
component: DashboardIndex,
})
const dashboardProfileRoute = createRoute({
getParentRoute: () => dashboardRoute, // Ota route sifatida dashboardRoute ko'rsatiladi
path: 'profile',
component: DashboardProfile,
})
const dashboardSettingsRoute = createRoute({
getParentRoute: () => dashboardRoute,
path: 'settings',
component: DashboardSettings,
})
// 3. Daraxtga qo'shish
const routeTree = rootRoute.addChildren([
dashboardRoute.addChildren([
dashboardIndexRoute,
dashboardProfileRoute,
dashboardSettingsRoute,
]),
])
export const router = createRouter({ routeTree })
3. Vizual arxitektura va Navigatsiya oqimi
Foydalanuvchi /dashboard/profile manzilidan /dashboard/settings manziliga o‘tganda nima sodir bo‘ladi?
flowchart TD
subgraph Browser["Brauzer oynasi"]
RootLayout["__root.tsx (Sayt Navbar va Footer)"]
subgraph DashLayout["dashboard.tsx (Dashboard Sidebar)"]
OutletSlot["<Outlet /> (O'zgaruvchan kontent)"]
end
end
UserAction["URL o'zgardi: /dashboard/profile -> /dashboard/settings"] --> OutletSlot
OutletSlot --> Swap["Faqatgina Settings sahifasi qayta chiziladi"]
DashLayout -.-> Keep["Sidebar o'z joyida saqlanadi (Re-render bo'lmaydi!)"]
4. Nima uchun Nested Routes bunchalik afzal?
1. Ma'lumotlarni parallel yuklash (Zero Waterfall)
React Router va boshqa kutubxonalarda ko‘pincha avval ota layout ma'lumotlari yuklanib bo‘lishi kutiladi, shundan so‘nggina ichki sahifa ma'lumotlari so‘raladi.
TanStack Router Route Tree orqali butun zanjirni avvaldan biladi. Shuning uchun /dashboard/profile ochilganda, ham Dashboardning, ham Profile sahifasining loader funksiyalari bir vaqtda parallel ravishda ishga tushadi!
2. Qayta render bo'lishdan himoya (Performance Boost)
Foydalanuvchi /dashboard/profiledan /dashboard/settingsga o‘tganda:
- Ota
DashboardLayoutkomponenti qaytadan unmount/mount bo‘lmaydi. - Sidebardagi scroll joylashuvi yoki ochilgan menyular holati (state) buzilmaydi.
- Faqatgina
<Outlet />ichidagi komponent almashtiriladi.
3. Kontekst va ma'lumotlarni meros qilib olish (Context Inheritance)
Ota route beforeLoad orqali login qilingan foydalanuvchi ma'lumotlarini yuklagan bo‘lsa, barcha bola routelar ushbu ma'lumotni hech qanday ortiqcha prop uzatmasdan to‘g‘ridan-to‘g‘ri ishlata oladi.
5. React Router va TanStack Router taqqosi
| Xususiyat | React Router | TanStack Router |
|---|---|---|
| Layoutni e'lon qilish | createBrowserRouter obyektida children: [...] orqali |
dashboard.tsx va dashboard/ papkasi orqali avtomatik |
| Loaderlar yuklanishi | Ko‘pincha ketma-ket (waterfall xavfi) | Doimo 100% parallel yuklanadi |
| Ichki yo'llarga havola | <Link to="profile"> (nisbiy yo‘llar noaniq bo‘lishi mumkin) |
<Link to="/dashboard/profile"> (To‘liq type-safe autocomplete) |
| Scroll holatini saqlash | Qo‘shimcha sozlash talab qilinadi | Ota layout DOM'da saqlangani uchun tabiiy ishlaydi |
Xulosa
- Nested Routes — umumiy ota layoutni saqlab qolgan holda ichki sahifalarni almashtirish uchun xizmat qiladi.
- Ota komponent ichidagi
<Outlet />bola sahifalar joylashadigan asosiy o‘rin hisoblanadi. - File-based tizimda
nom.tsxlayout vazifasini,nom/papkasi esa uning ichki sahifalarini bildiradi. - Ichma-ich marshrutlar parallel ma'lumot yuklash va keraksiz qayta renderlarning oldini olish orqali ilova unumdorligini oshiradi.