Series: TanStack Router Lesson 9

Route Tree — Route'lar daraxtini tashkil qilish

TanStack Router'da Route Tree: faylga asoslangan va kodga asoslangan marshrutlar daraxtini tuzish, getParentRoute, addChildren va ierarxiyaning afzalliklari.

9-dars

Route Tree — Route'lar daraxtini tashkil qilish

Tasavvur qiling, siz ko‘p qavatli yirik biznes markaziga kirdingiz. Binoga kirishda umumiy qabulxona (reception) va liftlar bor — bu ildiz poydevor (Root). 5-qavatga chiqsangiz, moliya bo‘limi o‘zining alohida eshigi va xodimlar koridoriga ega (Ota route / Layout). Uning ichida esa buxgalteriya, audit va xazina xonalari joylashgan (Bola routelar).

Veb-ilovalarda ham barcha sahifalar aynan mana shunday ota-bola ierarxiyasi bo‘yicha joylashadi. TanStack Router’da ushbu tizim Route Tree (Marshrutlar daraxti) deb ataladi. U ilovadagi har bir sahifaning o‘zaro qanday bog‘langanini va kim kimning ichida joylashganini aniq belgilab beradi.


1. File-based routing'da Route Tree qanday ishlaydi?

Agar siz File-based routing yondashuvini ishlatsangiz, papka va fayllar tuzilmasi avtomatik ravishda Route Tree'ga aylanadi. Siz hech qanday daraxtni qo‘lda yig‘maysiz — TanStack Router Vite plagini loyihadagi o‘zgarishlarni kuzatib boradi va orqa fonda src/routeTree.gen.ts faylini avtomatik yangilab turadi.

Papka tuzilishi misoli:

src/
└── routes/
    ├── __root.tsx          -> 1. Eng asosiy ildiz (Root)
    ├── index.tsx           -> 2. Asosiy sahifa ("/")
    ├── about.tsx           -> 3. Haqida sahifasi ("/about")
    └── dashboard/          
        ├── index.tsx       -> 4. Dashboard asosiy sahifasi ("/dashboard")
        └── settings.tsx    -> 5. Dashboard sozlamalari ("/dashboard/settings")

Ushbu papka tuzilmasidan TanStack Router avtomatik quyidagi vizual daraxtni hosil qiladi:

graph TD
    Root["__root.tsx (Umumiy Layout <Outlet/>)"] --> Index["/ (Asosiy sahifa)"]
    Root --> About["/about (Haqida)"]
    Root --> Dashboard["/dashboard (Dashboard Layout)"]
    Dashboard --> DashHome["/dashboard (Asosiy panel)"]
    Dashboard --> DashSettings["/dashboard/settings (Sozlamalar)"]

[!NOTE] dashboard/ papkasi o‘zining ichidagi settings.tsx fayli uchun ota (parent) hisoblanadi. Agar dashboard.tsx fayli yaratilsa, u ichki sahifalar uchun umumiy layout vazifasini bajaradi.


2. Code-based routing'da Route Tree'ni qo'lda yasash

Agar siz Code-based routing yondashuvini tanlasangiz, butun marshrutlar daraxtini dasturchi o‘z qo‘li bilan createRoute, getParentRoute va addChildren metodlari yordamida yig‘adi.

Bu usul TanStack Router qanday ishlashini ich-ichidan tushunish uchun eng yaxshi amaliyotdir:

// src/router.ts
import { 
  createRootRoute, 
  createRoute, 
  createRouter 
} from '@tanstack/react-router'

// 1. Eng asosiy ildiz route (Root)
const rootRoute = createRootRoute({
  component: RootComponent,
})

// 2. Root'ning bevosita bola sahifalari ("/" va "/about")
const indexRoute = createRoute({
  getParentRoute: () => rootRoute,
  path: '/',
  component: HomeComponent,
})

const aboutRoute = createRoute({
  getParentRoute: () => rootRoute,
  path: '/about',
  component: AboutComponent,
})

// 3. Dashboard ota layout route'i
const dashboardRoute = createRoute({
  getParentRoute: () => rootRoute,
  path: 'dashboard',
  component: DashboardLayout,
})

// 4. Dashboard ichidagi bola sahifa (Nested route)
const dashboardSettingsRoute = createRoute({
  getParentRoute: () => dashboardRoute, // DIQQAT: Ota route sifatida dashboardRoute ko'rsatiladi!
  path: 'settings',
  component: DashboardSettings,
})

// 5. Barcha shoxchalarni bitta umumiy daraxtga yig'ish (Route Tree)
const routeTree = rootRoute.addChildren([
  indexRoute,
  aboutRoute,
  dashboardRoute.addChildren([dashboardSettingsRoute]),
])

// 6. Router instansiyasiga Route Tree'ni uzatish
export const router = createRouter({ routeTree })

Muhim tushunchalar:

  • getParentRoute: Bu funksiya orqali bola route o‘zining otasini ko‘rsatadi. Bu TypeScript'ga ota sahifadagi kontekst, parametrlar va loader ma'lumotlarini bola sahifaga avtomatik meros qilib o‘tkazish (infer qilish) imkonini beradi.
  • addChildren([...]): Ota route'ga barcha bola route'larni fizik jihatdan ulab, yagona daraxt obyektini shakllantiradi.

3. Nima uchun Route Tree bunchalik muhim?

TanStack Router'dagi marshrutlar daraxti shunchaki sahifalar ro‘yxati emas. U ilovaning quyidagi uchta eng muhim mexanizmini boshqaradi:

1. 100% Type-Safety va Autocomplete

TanStack Router butun daraxtni statik ravishda bilgani uchun, ilovaning istalgan joyida <Link to="..."> yoki navigate({ to: "..." }) yozganingizda, IDE faqat ushbu daraxtda haqiqatan mavjud bo‘lgan manzillarnigina taklif qiladi:

import { Link } from '@tanstack/react-router'

export function Navigation() {
  return (
    <nav>
      {/* IDE avtomatik taklif beradi: "/", "/about", "/dashboard/settings" */}
      <Link to="/dashboard/settings">Sozlamalar</Link>

      {/* XATO! TypeScript ruxsat bermaydi, chunki bunday yo'l daraxtda yo'q: */}
      {/* <Link to="/profile/billing">Hisob-kitob</Link> */}
    </nav>
  )
}

2. Layout'larni avtomatik meros qilib olish (Inheritance)

Ota route (masalan, /dashboard) o‘zining yon menyusi (Sidebar) va sarlavhasiga (Header) ega bo‘lsa, uning ichidagi barcha bola sahifalar (/dashboard/settings, /dashboard/analytics) avtomatik ravishda ushbu layout ichidagi <Outlet />da chiziladi. Kodni takrorlash shart emas.

flowchart LR
    A["/dashboard URL chaqirildi"] --> B["DashboardLayout chiziladi"]
    B --> C["&lt;Outlet /&gt; ichida DashboardSettings ochiladi"]

3. Parallel va tartibli ma'lumot yuklash (Zero Waterfall)

React Router va an'anaviy kutubxonalarda ko‘pincha avval ota sahifa yuklanadi, keyin esa bola sahifaning ma'lumot so‘rovi boshlanadi (Waterall effekti).

TanStack Router Route Tree orqali foydalanuvchi qaysi nuqtaga kirayotganini boshidanoq biladi. Shu sababli ota va bola sahifaning barcha loader funksiyalarini bir vaqtning o‘zida parallel ravishda ishga tushiradi:

sequenceDiagram
    autonumber
    actor User as Foydalanuvchi
    participant Router as TanStack Router
    participant API as Backend Server

    User->>Router: /dashboard/settings sahifasiga o'tdi
    Note over Router,API: Waterfall YO'Q! So'rovlar parallel ketadi:
    par Parallel yuklanish
        Router->>API: Dashboard ma'lumotlarini yuklash (Ota)
    and
        Router->>API: Settings ma'lumotlarini yuklash (Bola)
    end
    API-->>Router: Har ikkala javob qaytdi
    Router-->>User: Tayyor sahifa bir vaqtda ekranga chizildi

4. File-based vs Code-based Route Tree taqqosi

Xususiyat File-based Route Tree Code-based Route Tree
Yaratilish usuli Papka/fayllar orqali avtomatik (routeTree.gen.ts) Dasturchi tomonidan qo‘lda (addChildren)
Katta loyihalarda qulaylik Juda yuqori (fayl qo‘shish bilan route tayyor) O‘rtacha (har bir yangi sahifani qo‘lda ulash kerak)
Moslashuvchanlik Papka nomlash konvensiyalariga tayanadi Kod orqali to‘liq erkin boshqariladi
Type-Safety 100% to‘liq va avtomatik 100% to‘liq (getParentRoute orqali)
Tavsiya etilgan holat Standart va katta React ilovalari uchun Kichik loyihalar yoki maxsus arxitekturalar uchun

Xulosa

  • Route Tree — bu ilovaning barcha marshrutlari, ota-bola bog‘liqliklari va layoutlarini birlashtiruvchi markaziy ierarxik daraxtdir.
  • File-based routingda daraxt papka strukturasi asosida avtomatik shakllanadi (routeTree.gen.ts).
  • Code-based routingda daraxt getParentRoute va rootRoute.addChildren([...]) yordamida dasturchi tomonidan yig‘iladi.
  • Route Tree tufayli TanStack Router 100% Type-safety, tartibli Layout merosi va eng muhimi ma'lumotlarni parallel yuklash (No Waterfall) imkoniyatini taqdim etadi.