Type-safe route patterns — Route parametrlarini va route API'larini tipizatsiya qilish
React Router'da type-safe route patterns: stringly-typed URL xatolarini yo'qotish, Route Helper / Path Builder pattern, refactoring xavfsizligi va markazlashgan yo'llar boshqaruvi.
63-dars
Type-safe route patterns — Route parametrlarini va route API'larini tipizatsiya qilish
Tasavvur qiling, siz yirik xalqaro logistika markazida dispetchersiz. Har kuni yuzlab yuk mashinalarini turli manzillarga jo‘natasiz:
- Xavfli usul (Qo‘lda yozish): Haydovchining yo‘l varaqasiga manzilni qo‘lda shoshilib yozib berasiz. Agar bitta harfni adashtirib
/dashboad/candiddates/42deb yozib yuborsangiz, haydovchi adashib boshqa shaharga ketib qoladi yoki yopiq yo‘lga (404 xatosiga) duch keladi. - Xavfsiz usul (Type-Safe avtomatika): Siz maxsus kompyuter tizimidan tayyor marshrut shablonini tanlaysiz. Tizim sizdan mijozning ID raqamini kiritishni talab qiladi. Raqam kiritilmaguncha yo‘l varaqasi chop etilmaydi va bitta ham harfiy xatoga yo‘l qo‘yilmaydi!
React Router ilovalarida ham eng ko‘p uchraydigan muammolardan biri — bu "Stringly-typed" (oddiy matn ko‘rinishidagi) URL manzillar bilan ishlashdir. Type-Safe Route Patterns — bu barcha marshrutlar va ularning parametrlarini yagona markazlashgan qat'iy turlarga bog‘lab chiqish uslubidir.
"Stringly-typed" muammo o'zi nima?
Klassik React loyihalarida havolalar va navigatsiya funksiyalari shunday yoziladi:
// ❌ XAVFLI: Harfiy xato (Typo) bor, lekin TypeScript hech qanday xato bermaydi!
navigate("/dashbord/candiddates/42");
// ❌ XAVFLI: Parametr berish unutilgan (/candidates/undefined bo'lib ketadi!)
navigate(`/dashboard/candidates/${candidateId}`);
Agar ertaga loyiha menejeri kelib: "Biz /dashboard yo‘lini /admin deb o‘zgartiramiz" desa, siz butun loyihangizdagi 150 ta fayldan qo‘lda matn qidirib, bittalab to‘g‘rilab chiqishingiz kerak bo‘ladi. Birorta joy esdan chiqsa — 404 xatosi kafolatlangan!
flowchart LR
subgraph BadWay["❌ Stringly-Typed Navigatsiya"]
A["navigate('/dashbaord/candidates')"] --> B["Bitta harf xato!"]
B --> C["Kompilyator xatoni sezmaydi"]
C --> D["Foydalanuvchi ekranda 404 xatosini ko'radi"]
end
subgraph GoodWay["✅ Type-Safe Path Builder"]
E["navigate(ROUTES.candidates.detail(id))"] --> F["Avtomatik to'ldirish (IntelliSense)"]
F --> G["Parametr qat'iy talab qilinadi"]
G --> H["0 ta xato, 100% to'g'ri manzil"]
end
1. Yechim: Path Builder (Route Helper) Pattern
Sanoatdagi eng ommabop, qulay va xavfsiz yechim — bu barcha yo‘llarni boshqaradigan markazlashgan ROUTES obyektini yaratishdir:
// src/config/routes.ts
export const ROUTES = {
home: () => "/" as const,
login: () => "/login" as const,
dashboard: {
root: () => "/dashboard" as const,
candidates: {
list: () => "/dashboard/candidates" as const,
// Dinamik parametr majburiy qilib belgilanadi!
detail: (candidateId: string | number) => `/dashboard/candidates/${candidateId}` as const,
edit: (candidateId: string | number) => `/dashboard/candidates/${candidateId}/edit` as const,
},
settings: () => "/dashboard/settings" as const,
},
} as const;
2. Router konfiguratsiyasida ishlatish
Router sozlamasida ham xuddi shu obyekt shablonlaridan foydalanamiz:
// src/routes.tsx
import { createBrowserRouter } from "react-router-dom";
import { ROUTES } from "./config/routes";
import MainLayout from "./layouts/MainLayout";
import CandidatesList from "./pages/CandidatesList";
import CandidateDetail from "./pages/CandidateDetail";
import CandidateEdit from "./pages/CandidateEdit";
export const router = createBrowserRouter([
{
path: ROUTES.dashboard.root(),
element: <MainLayout />,
children: [
{
path: "candidates",
element: <CandidatesList />,
},
{
// Shablon: /dashboard/candidates/:candidateId
path: "candidates/:candidateId",
element: <CandidateDetail />,
},
{
path: "candidates/:candidateId/edit",
element: <CandidateEdit />,
},
],
},
]);
3. Komponentlar ichida xavfsiz navigatsiya
Endi komponentlar ichida xoh <Link>, xoh useNavigate bo‘lsin, hech qachon xom matn (string) yozilmaydi:
// src/components/CandidateRow.tsx
import { Link, useNavigate } from "react-router-dom";
import { ROUTES } from "../config/routes";
export interface Candidate {
id: number;
name: string;
role: string;
}
export function CandidateRow({ candidate }: { candidate: Candidate }) {
const navigate = useNavigate();
function handleEdit() {
// 🛡️ TypeScript tekshiradi: Agar candidate.id berilmasa, kod build bo'lmaydi!
navigate(ROUTES.dashboard.candidates.edit(candidate.id));
}
return (
<div style={{ display: "flex", justifyContent: "space-between", padding: "10px", borderBottom: "1px solid #eee" }}>
<span>{candidate.name}</span>
<div style={{ display: "flex", gap: "10px" }}>
{/* 1. Link orqali xavfsiz o'tish */}
<Link
to={ROUTES.dashboard.candidates.detail(candidate.id)}
style={{ color: "#2563eb", textDecoration: "none" }}
>
Profilni ko'rish
</Link>
{/* 2. Dasturiy navigatsiya */}
<button onClick={handleEdit}>
Tahrirlash
</button>
</div>
</div>
);
}
export default CandidateRow;
4. Query parametrlarni Type-Safe qilish
Faqat yo‘l parametrlari emas, balki qidiruv (Search / Query) parametrlarini ham funksiya argumenti sifatida tiplashtirish mumkin:
// src/config/routes.ts kengaytmasi
export interface CandidatesFilter {
page?: number;
search?: string;
status?: "active" | "inactive";
}
export const ROUTES = {
// ...
candidatesWithFilter: (filters?: CandidatesFilter) => {
const params = new URLSearchParams();
if (filters?.page) params.set("page", String(filters.page));
if (filters?.search) params.set("search", filters.search);
if (filters?.status) params.set("status", filters.status);
const queryString = params.toString();
return `/dashboard/candidates${queryString ? `?${queryString}` : ""}` as const;
},
};
// Ishlatilishi:
ROUTES.candidatesWithFilter({ page: 2, status: "active" });
// Natija: /dashboard/candidates?page=2&status=active
Nima uchun bu juda muhim?
| Mezon | Oddiy String Navigatsiya | Type-Safe Route Patterns |
|---|---|---|
| Harfiy xatolar (Typo) | Juda ko‘p uchraydi, 404 xatolariga sabab bo‘ladi | 0% xato, kod muharriri o‘zi yozib beradi |
| Parametrlar nazorati | id unutib qoldirilsa ham sezilmaydi |
Parametr berilmasa TypeScript ogohlantiradi |
| Refactoring tezligi | Kunlab vaqt oladi, qidiruv xatarlari yuqori | 1 daqiqa: Faqat ROUTES obyektida o‘zgartiriladi |
| Katta jamoada ishlash | Yangi dasturchi qaysi sahifa qayerda joylashganini bilmay qiynaladi | ROUTES. deb yozishi bilan butun sayt xaritasi chiqadi |
Xulosa
- URL manzillarini oddiy matn (
"/path/...") ko‘rinishida yozish katta loyihalarda xatoliklar va 404 sahifalarga olib keluvchi eng asosiy manbalardan biridir. - Path Builder pattern (
ROUTES) orqali barcha yo‘llar va ularning dinamik parametrlarini markazlashtirib tiplashtirish tavsiya etiladi. - Ushbu yondashuv loyihangizni toza, o‘zgartirishlarga chidamli (refactor-safe) va jamoa uchun nihoyatda qulay holatga keltiradi.