Isolated Form Components — Mustaqil field komponentlarini tashkil qilish
Formadagi har bir inputni useFormState va FieldPath orqali alohida izolyatsiya qilingan komponent sifatida qurish, re-renderlarni nolga tushirish va dizayn tizimiga integratsiya.
96-dars
Isolated Form Components — Mustaqil field komponentlarini tashkil qilish
Oldingi darslarda useWatch() va useFormState() yordamida formaning butun boshli bo'limlari (sections), narx hisoblagichlari (calculators) yoki submit tugmasini alohida izolyatsiya qilishni ko'rgan edik.
Isolated Form Components (izolyatsiya qilingan maydon komponentlari) yondashuvida esa bu falsafa eng kichik atomik darajaga — bevosita har bir alohida input komponenti darajasiga tushiriladi. Har bir IsolatedTextField yoki IsolatedSelect komponenti o'zining qiymatini, validatsiya xatosini (errors), nofaol holatini (disabled / isSubmitting) va re-render davrini o'z ichida to'liq mustaqil boshqaradi.
1. Nega Isolated Field Components kerak?
An'anaviy yondashuvda ota komponentda const { formState: { errors } } = useForm() deb yoziladi. Buning oqibatida:
- Foydalanuvchi
workEmailmaydonida xato qilsa, butun ota forma va uning ichidagifullName,phone,departmentkabi 30 ta boshqa inputlar ham qayta render bo'ladi. - Inputlar ko'paygani sari matn terishda sezilarli sekinlashuv (typing latency) yuzaga keladi.
graph TD
subgraph Ananaviy_Field["An'anaviy Forma: Ota komponentda errors o'qiladi"]
A1["Email xato kiritildi"] --> B1["Ota Forma errors o'zgardi"]
B1 --> C1["Ota Forma to'liq Re-render"]
C1 --> D1["FullName Re-render"]
C1 --> E1["WorkEmail Re-render"]
C1 --> F1["Department Re-render"]
end
subgraph Izolyatsiyalangan_Field["Isolated Form Components: useFormState(name)"]
A2["Email xato kiritildi"] --> B2["RHF Ichki Store yangilandi"]
B2 --> C2["Ota Forma: 0 ta re-render (Tinch)"]
B2 --> D2["FullName: 0 ta re-render (Tinch)"]
B2 --> E2["Department: 0 ta re-render (Tinch)"]
B2 -->|Faqat o'sha field| F2["WorkEmail komponenti mustaqil qizaradi va xabar chiqaradi"]
end
2. Arxitekturaning 3 ta asosiy ustuni
useFormState({ control, name, exact: true }): Komponent faqat o'ziningnameparametrida ko'rsatilgan maydon bo'yichaerrorsvaisSubmittingo'zgarishlariga obuna bo'ladi.FieldPath<TFormValues>: TypeScript generic orqali har qanday shakl obyektidagi mavjud to'g'ri maydon nomlarini avtomatik taklif qiladi (noto'g'ri nom yozilsa, compile-time xato beradi).RegisterOptions<TFormValues, TName>: Har bir maydonga xos bo'lgan validatsiya qoidalarini (required,pattern,minLength) to'liq type-safe uzatish imkonini beradi.
3. To'liq amaliy misol: Katta Onboarding formasi
Quyidagi amaliy misolda generic IsolatedTextField yaratilgan. Har bir maydon o'zining render hisoblagichiga ega (RenderBadge). Masalan, email maydonida xatolik yuz berganda faqatgina o'sha workEmail komponenti qayta render bo'ladi, boshqa maydonlar va ota forma tinch qoladi:
import React, { useRef } from "react";
import {
useForm,
useFormState,
type Control,
type FieldPath,
type FieldValues,
type RegisterOptions,
type UseFormRegister,
type SubmitHandler,
} from "react-hook-form";
// 1. Forma ma'lumotlari modeli
type EmployeeOnboardingValues = {
fullName: string;
workEmail: string;
department: string;
phoneNumber: string;
};
// Re-render hisoblagich nishoni
function RenderBadge({ name }: { name: string }) {
const renders = useRef(0);
renders.current += 1;
return (
<span className="text-xs px-2 py-0.5 rounded bg-gray-100 text-gray-700 font-mono">
{name}: {renders.current} render
</span>
);
}
// 2. Generic IsolatedTextField komponentining Props tipi
type IsolatedTextFieldProps<
TFormValues extends FieldValues,
TName extends FieldPath<TFormValues> = FieldPath<TFormValues>
> = {
name: TName;
label: string;
placeholder?: string;
type?: "text" | "email" | "tel";
control: Control<TFormValues>;
register: UseFormRegister<TFormValues>;
rules?: RegisterOptions<TFormValues, TName>;
};
// 3. Mustaqil va Izolyatsiya qilingan Input Komponenti
function IsolatedTextField<
TFormValues extends FieldValues,
TName extends FieldPath<TFormValues> = FieldPath<TFormValues>
>({
name,
label,
placeholder,
type = "text",
control,
register,
rules,
}: IsolatedTextFieldProps<TFormValues, TName>) {
// Faqat aynan shu maydonga tegishli errors va submit holatiga obuna bo'lamiz
const { errors, isSubmitting } = useFormState({
control,
name,
exact: true,
});
// Nested (ichma-ich) maydonlar xatosini xavfsiz o'qish (masalan "user.email")
const fieldError = (name as string)
.split(".")
.reduce<unknown>((acc, part) => {
if (acc && typeof acc === "object" && part in acc) {
return (acc as Record<string, unknown>)[part];
}
return undefined;
}, errors as unknown) as { message?: string } | undefined;
const hasError = Boolean(fieldError);
return (
<div className="space-y-1">
<div className="flex items-center justify-between">
<label className="block text-sm font-medium text-gray-700">
{label} {rules?.required ? <span className="text-rose-500">*</span> : null}
</label>
<RenderBadge name={name as string} />
</div>
<input
type={type}
disabled={isSubmitting}
placeholder={placeholder}
{...register(name, rules)}
className={`w-full px-3 py-2 border rounded-lg outline-none transition text-sm ${
hasError
? "border-rose-500 focus:ring-2 focus:ring-rose-200"
: "border-gray-300 focus:ring-2 focus:ring-blue-200 focus:border-blue-500"
} disabled:bg-gray-100 disabled:cursor-not-allowed`}
/>
{fieldError?.message && (
<p className="text-xs text-rose-600 font-medium">{fieldError.message}</p>
)}
</div>
);
}
// 4. Asosiy Ota Forma
export function IsolatedFormComponentsExample() {
const {
register,
control,
handleSubmit,
formState: { isSubmitting },
} = useForm<EmployeeOnboardingValues>({
mode: "onBlur",
defaultValues: {
fullName: "",
workEmail: "",
department: "Frontend Dasturchi",
phoneNumber: "",
},
});
const onSubmit: SubmitHandler<EmployeeOnboardingValues> = async (data) => {
await new Promise((r) => setTimeout(r, 800));
console.log("Xodim muvaffaqiyatli ro'yxatdan o'tkazildi:", data);
alert("Ma'lumotlar saqlandi!");
};
return (
<div className="max-w-md mx-auto p-6 bg-white rounded-xl shadow-lg space-y-6">
<div className="flex items-center justify-between border-b pb-3">
<h2 className="text-lg font-bold text-gray-900">Yangi Xodim Ro'yxati</h2>
<RenderBadge name="Ota Forma" />
</div>
<form onSubmit={handleSubmit(onSubmit)} className="space-y-4">
{/* Mustaqil To'liq Ism Maydoni */}
<IsolatedTextField
name="fullName"
label="To'liq ism"
placeholder="Masalan: Sardorbek Aliyev"
control={control}
register={register}
rules={{
required: "Ism familiya kiritilishi shart",
minLength: { value: 3, message: "Kamida 3 ta harf bo'lsin" },
}}
/>
{/* Mustaqil Ish Emaili Maydoni */}
<IsolatedTextField
name="workEmail"
label="Ish emaili"
type="email"
placeholder="[email protected]"
control={control}
register={register}
rules={{
required: "Ish emaili majburiy",
pattern: {
value: /^[^\s@]+@[^\s@]+\.[^\s@]+$/,
message: "Email manzili formati xato",
},
}}
/>
{/* Mustaqil Telefon Raqami Maydoni */}
<IsolatedTextField
name="phoneNumber"
label="Telefon raqami"
type="tel"
placeholder="+998 90 123 45 67"
control={control}
register={register}
rules={{
required: "Telefon raqami majburiy",
}}
/>
{/* Mustaqil Bo'lim Maydoni */}
<IsolatedTextField
name="department"
label="Lavozim / Bo'lim"
placeholder="Masalan: Mobile Developer"
control={control}
register={register}
rules={{
required: "Bo'lim ko'rsatilishi shart",
}}
/>
<button
type="submit"
disabled={isSubmitting}
className="w-full py-2.5 px-4 bg-blue-600 hover:bg-blue-700 disabled:bg-gray-400 text-white font-medium rounded-lg transition"
>
{isSubmitting ? "Saqlanmoqda..." : "Xodimni ro'yxatga olish"}
</button>
</form>
</div>
);
}
4. Dizayn Tizimi (Design System) va UI Kit Uchun Qo'llash
Kompaniya yoki loyiha miqyosida umumiy UI Kit yaratayotganda ushbu yondashuv juda katta yutuq beradi:
- Barcha inputlar (
IsolatedTextField,IsolatedSelect,IsolatedTextarea,IsolatedSwitch) bir xil interfeys va xatolik ko'rsatish uslubiga ega bo'ladi. - Loyihadagi boshqa dasturchilar xatolarni qanday chiqarish yoki
formStateni qanday ulash haqida bosh qotirmaydi — shunchakiname,controlvaregisteruzatishadi. - Katta jadvalli tahrirlashda (Inline Table Editing) 100 ta qator bo'lsa ham, bitta katakcha qizarganda butun jadval qotib qolmaydi.
5. Qachon Ishlatish Kerak va Qachon Shart Emas?
| Stsenariy | Isolated Components Ishlatish Tavsiya Qilinadimi? | Sababi |
|---|---|---|
| Katta CRM / ERP formalar (30-100+ maydon) | Ha (Tavsiya etiladi) | Klaviaturada qotishlar bo'lmasligi va silliq ishlash uchun |
| Umumiy UI Kit / Dizayn tizimi | Ha (Standart usul) | Qayta ishlatiluvchanlik va qat'iy standart uchun |
| Oddiy Login yoki Qidiruv formasi (1-2 maydon) | Yo'q (Ortiqcha kod) | Oddiy register() va ota komponentdagi errors yetarli |
Xulosa
- Isolated Form Components — formadagi har bir maydonga o'z holatini o'zi boshqarish huquqini beradi.
useFormState({ control, name, exact: true })— xatolik va holat o'zgarishlarini faqat aynan o'sha maydon ichida ushlab qoladi.- Unumdorlik: Ota komponentda
errorso'qilmagani sababli, validatsiya xatolari chiqqanda qo'shni maydonlar 0 ta re-render bilan ishlaydi.