Seriya: React Hook Form Dars 95

FormProvider Performance — Context orqali form state uzatishning ta'siri

React Context va FormProvider ning ishlash mexanizmi, barqaror metodlar (stable references), re-render afsonalari va useFormContext unumdorligi.

95-dars

FormProvider Performance — Context orqali form state uzatishning ta'siri

React ishlab chiquvchilari orasida shunday keng tarqalgan xavotir bor: "Agar formani React Context (FormProvider) bilan o'rab qo'ysak, formadagi bitta inputga harf yozilganda Context Value yangilanib, Provider ichidagi barcha komponentlar boshdan-oyoq re-render bo'lmaydimi?"

Qisqa va aniq javob: Yo'q, qayta render bo'lmaydi!

React Hook Form'ning FormProvider komponenti standart React holatiga (useState) emas, balki barqaror havolalar (stable references) va ichki obunalar (subscriptions) mexanizmiga tayanadi. Keling, uning kapot ostida qanday ishlashini va unumdorlik sirlarini batafsil tahlil qilamiz.


1. Nega FormProvider butun daraxtni qayta render qilmaydi?

Oddiy React ilovalarida Context ichidagi value o'zgarganda barcha useContext chaqirgan komponentlar qayta render bo'ladi. Ammo React Hook Form'da holat quyidagicha tashkil etilgan:

graph TD
  subgraph Ananaviy_Context["Oddiy React Context (useState)"]
    A1["Foydalanuvchi yozdi"] --> B1["setFormState(newState)"]
    B1 --> C1["Context Value o'zgardi (yangi object reference)"]
    C1 --> D1["Provider ichidagi BARCHA komponentlar Re-render!"]
  end

  subgraph RHF_FormProvider["React Hook Form FormProvider"]
    A2["Foydalanuvchi yozdi"] --> B2["DOM Event / Ref yangilandi"]
    B2 --> C2["Context Value (methods) O'ZGARMAYDI (Reference barqaror)"]
    C2 --> D2["Qo'shni bo'limlar: 0 ta re-render (Tinch)"]
    B2 -->|Targeted Subscription| E2["Faqat tegishli useWatch / useFormState yangilanadi"]
  end

Unumdorlikning 3 ta ustuni:

  1. Methods doimiyligi: useForm() dan qaytuvchi register, setValue, getValues, control, trigger kabi funksiyalar referensial jihatdan barqaror (stable). Ular har safar qayta yaratilmaydi.
  2. Qiymatlar Context'da saqlanmaydi: Formadagi matnlar, sonlar yoki sanalar Context valuesida saqlanmaydi — ular RHF ning ichki Subject do'konida (store) turadi.
  3. Targeted Subscriptions: Har bir ichki komponent o'zining register(), useWatch() yoki useFormState() chaqiruvi orqali faqat o'ziga kerakli o'zgarishgagina mustaqil obuna bo'ladi.

2. Haqiqiy re-render sabablari qayerdan keladi?

Agar loyihangizda FormProvider ichidagi hamma komponentlar harf yozganda miltillayotgan (re-render bo'layotgan) bo'lsa, ayb FormProviderda emas, balki ichki komponentlarning noto'g'ri yozilganidadir:

Noto'g'ri yondashuv (Anti-pattern) Oqibati To'g'ri yechim
const { watch } = useFormContext(); const all = watch(); O'sha bo'lim har qanday input o'zgarganda qayta chiziladi Kerakli maydonni useWatch({ name: "..." }) bilan o'qing
const { formState } = useFormContext(); barcha narsani o'qish Har bir validatsiya va dirty o'zgarishida render bo'ladi Faqat kerakli parametrni destructure qiling yoki useFormState ishlating
Ota formada FormProvider yoniga keraksiz useState qo'yish Ota formadagi useState butun Provider daraxtini majburan render qiladi Formaga tegishli holatlarni React Hook Form do'konida qoldiring

3. FormProvider ning Katta Loyihalardagi Afzalliklari

  1. Props Drilling ga chek qo'yadi: 5-10 qavat chuqurlikdagi komponentlarga control, register, errors larni uzatib yurish shart emas.
  2. Modul arxitektura: Shakllar bo'limlarga (ProfileSection, BillingSection, SecuritySettings) oson ajratiladi.
  3. To'liq Type-Safety: Ichki komponentlarda useFormContext<T>() orqali barcha maydonlar va xatolar to'liq tiplashtiriladi.

4. To'liq amaliy misol: Sozlamalar markazi (Account Settings)

Quyidagi amaliy misolda asosiy sahifa FormProvider bilan o'ralgan. Profil bo'limi, bildirishnomalar bo'limi va xavfsizlik bo'limlari mustaqil ajratilgan. Har bir bo'limning render sonini RenderBadge orqali kuzatishingiz mumkin:

import React, { useRef } from "react";
import {
  FormProvider,
  useForm,
  useFormContext,
  useWatch,
  useFormState,
  type SubmitHandler,
} from "react-hook-form";

// 1. Formaning umumiy tiplari
type AccountSettingsValues = {
  displayName: string;
  email: string;
  emailAlerts: boolean;
  slackWebhook: string;
  twoFactorAuth: boolean;
};

// 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. Profil bo'limi: Faqat ism va email bilan ishlaydi
function ProfileSection() {
  const {
    register,
    formState: { errors },
  } = useFormContext<AccountSettingsValues>();

  return (
    <section className="border border-gray-200 bg-white p-5 rounded-xl shadow-sm space-y-4">
      <div className="flex items-center justify-between border-b pb-2">
        <h3 className="font-semibold text-gray-800">Profil ma'lumotlari</h3>
        <RenderBadge name="ProfileSection" />
      </div>

      <div>
        <label className="block text-sm font-medium text-gray-700 mb-1">
          Ko'rinadigan ism *
        </label>
        <input
          {...register("displayName", { required: "Ism kiritilishi shart" })}
          placeholder="Masalan: Sardorbek"
          className="w-full px-3 py-2 border rounded-lg focus:ring-2 focus:ring-blue-500 outline-none"
        />
        {errors.displayName && (
          <p className="text-xs text-rose-500 mt-1">{errors.displayName.message}</p>
        )}
      </div>

      <div>
        <label className="block text-sm font-medium text-gray-700 mb-1">
          Email manzil *
        </label>
        <input
          type="email"
          {...register("email", { required: "Email kiritilishi shart" })}
          placeholder="[email protected]"
          className="w-full px-3 py-2 border rounded-lg focus:ring-2 focus:ring-blue-500 outline-none"
        />
        {errors.email && (
          <p className="text-xs text-rose-500 mt-1">{errors.email.message}</p>
        )}
      </div>
    </section>
  );
}

// 3. Bildirishnomalar bo'limi: Faqat emailAlerts o'zgarganda shartli Slack maydoni yangilanadi
function NotificationSection() {
  const { register, control } = useFormContext<AccountSettingsValues>();

  // Izolyatsiya qilingan obuna
  const emailAlerts = useWatch({
    control,
    name: "emailAlerts",
  });

  return (
    <section className="border border-gray-200 bg-white p-5 rounded-xl shadow-sm space-y-4">
      <div className="flex items-center justify-between border-b pb-2">
        <h3 className="font-semibold text-gray-800">Bildirishnomalar</h3>
        <RenderBadge name="NotificationSection" />
      </div>

      <label className="flex items-center gap-3 cursor-pointer">
        <input
          type="checkbox"
          {...register("emailAlerts")}
          className="w-4 h-4 text-blue-600 rounded"
        />
        <span className="text-sm text-gray-700 font-medium">
          Muhim hodisalar haqida email xabarnomalarini olish
        </span>
      </label>

      {/* Shartli maydon: faqat emailAlerts true bo'lsa ko'rinadi */}
      {emailAlerts && (
        <div className="pt-2 border-t border-dashed border-gray-200">
          <label className="block text-sm font-medium text-gray-700 mb-1">
            Qo'shimcha Slack Webhook (ixtiyoriy)
          </label>
          <input
            {...register("slackWebhook")}
            placeholder="https://hooks.slack.com/services/..."
            className="w-full px-3 py-2 border rounded-lg focus:ring-2 focus:ring-blue-500 outline-none text-sm"
          />
        </div>
      )}
    </section>
  );
}

// 4. Pastki Harakatlar Paneli: useFormState orqali izolyatsiya qilingan
function SaveActionBar() {
  // control prop berilmasa ham FormProvider kontekstidan o'zi oladi!
  const { isDirty, isSubmitting } = useFormState<AccountSettingsValues>();

  return (
    <div className="flex items-center justify-between p-4 bg-gray-50 border rounded-xl">
      <div className="flex items-center gap-2">
        <span className="text-xs text-gray-600">
          {isDirty ? "Saqlanmagan o'zgarishlar mavjud" : "Barcha o'zgarishlar saqlangan"}
        </span>
        <RenderBadge name="ActionBar" />
      </div>

      <button
        type="submit"
        disabled={isSubmitting || !isDirty}
        className="px-6 py-2 bg-blue-600 hover:bg-blue-700 disabled:bg-gray-300 text-white font-medium rounded-lg transition"
      >
        {isSubmitting ? "Saqlanmoqda..." : "Saqlash"}
      </button>
    </div>
  );
}

// 5. Asosiy Ota Forma
export function FormProviderPerformanceExample() {
  const methods = useForm<AccountSettingsValues>({
    mode: "onBlur",
    defaultValues: {
      displayName: "",
      email: "",
      emailAlerts: true,
      slackWebhook: "",
      twoFactorAuth: false,
    },
  });

  const onSubmit: SubmitHandler<AccountSettingsValues> = async (data) => {
    await new Promise((r) => setTimeout(r, 700));
    console.log("Sozlamalar saqlandi:", data);
    methods.reset(data); // isDirty ni qayta false qilish
  };

  return (
    <div className="max-w-xl mx-auto p-6 space-y-6">
      <div className="flex items-center justify-between">
        <h2 className="text-xl font-bold text-gray-900">Hisob Sozlamalari</h2>
        <RenderBadge name="Root Form" />
      </div>

      {/* FormProvider butun ichki tizimni stable metodlar bilan ta'minlaydi */}
      <FormProvider {...methods}>
        <form onSubmit={methods.handleSubmit(onSubmit)} className="space-y-4">
          <ProfileSection />
          <NotificationSection />
          <SaveActionBar />
        </form>
      </FormProvider>
    </div>
  );
}

5. FormProvider Ishlatishda Muhim Maslahatlar

  1. Har doim useFormContext<T>() ga generic tip bering:
    // Type-safe va avtomatik takliflar (autocomplete) beradi:
    const { register } = useFormContext<AccountSettingsValues>();
    
  2. Kichik, mustaqil formalarda ortiqcha murakkablashtirmang: Agar bitta sahifada 3 ta bir-biriga bog'liq bo'lmagan mustaqil kichik formalar (masalan, qidiruv inputi, fikr-mulohaza modali va login formasi) bo'lsa, ularni bitta umumiy FormProviderga solmang. Har birining o'z useForm()i bo'lishi ancha qulayroq.
  3. useFormState() da control ixtiyoriy: FormProvider ichida joylashgan istalgan bola komponentda useFormState() chaqirganda control parametrini berish shart emas — u avtomatik ravishda kontekstdan olinadi.

Xulosa

  • FormProvider sekinlashtirmaydi: React Hook Form konteksti orqali holat emas, barqaror metodlar va subscription havolalari uzatiladi.
  • Renderlar izolyatsiyalangan: Bitta bo'limdagi inputga yozish qo'shni bo'limlarni qayta chizilishiga olib kelmaydi.
  • Katta va ko'p qavatli formalarda standart: Wizard, tablar va chuqur tuzilmali sahifalarda kodni toza saqlash va props drillingdan qutulishning eng to'g'ri yo'lidir.