Series: React Hook Form Lesson 52

Custom Validation Rules — Murakkab va shartli validatsiya qoidalari

register validate opsiyasi, cross-field bog'liqliklar, shartli majburiylik, named rules obyektlari va trigger bilan qayta tekshirish.

52-dars

Custom Validation Rules — Murakkab validation qoidalari

Custom Validation Rules (Maxsus validatsiya qoidalari) — bu register(name, { validate: ... }) opsiyasi yordamida standart required, minLength yoki pattern kabi qoidalar bilan ifodalab bo'lmaydigan murakkab, shartli yoki bir nechta maydon o'rtasidagi (cross-field) biznes mantiqlarini tekshirish mexanizmidir.

validate parametri ikki xil usulda berilishi mumkin:

  1. Bitta funksiya ko'rinishida: validate: (value, formValues) => boolean | string | Promise<...>
  2. Nomlangan qoidalar (Named rules) obyekti: validate: { ruleA: (v, fv) => ..., ruleB: (v, fv) => ... } — bir nechta alohida qoidani aniq nomlab, xato turi (errors.field.type) orqali ajratish uchun.

1. Murakkab qoidalarda eng ko'p uchraydigan ssenariylar

Ssenariy Nimani tekshiradi? Qanday yoziladi?
Cross-field bog'liqlik Boshqa maydon qiymatiga qarab shart (masalan: endDate >= startDate yoki yangi parol eski parolga teng emasligi). (value, formValues) => ... ichida formValues orqali boshqa maydonni solishtirish.
Shartli (conditional) majburiylik Muayyan tanlovga qarab maydonning majburiy bo'lishi (masalan: accountType === "business" bo'lsa companyName shart). formValues.accountType qiymatini tekshirib, shart bajarilmasa xato qaytarish.
Ko'p bosqichli format va biznes qoidalar Taklif kodi formati, parol murakkabligi yoki maxsus belgilar borligini alohida tekshirish. Named validator obyektida { minChars: ..., upperAndDigit: ... } ko'rinishida.

2. Real misol: Shartli maydon, sanalar taqqoslanishi va named rules

Quyidagi misolda:

  • accountType === "business" tanlanganda companyName majburiy bo'ladi;
  • endDate sanasi startDate dan oldin bo'lmasligi formValues.startDate orqali tekshiriladi;
  • inviteCode maydonida bir nechta alohida nomlangan (named) validatsiya qoidasi qo'llaniladi:
import { useForm, type SubmitHandler } from "react-hook-form";

type SprintAccessFormValues = {
  accountType: "personal" | "business";
  companyName: string;
  startDate: string;
  endDate: string;
  inviteCode: string;
};

export function CustomValidationRulesForm() {
  const {
    register,
    trigger,
    handleSubmit,
    formState: { errors, isSubmitting },
  } = useForm<SprintAccessFormValues>({
    mode: "onChange",
    defaultValues: {
      accountType: "personal",
      companyName: "",
      startDate: "2026-11-20",
      endDate: "2026-11-27",
      inviteCode: "",
    },
  });

  const onSubmit: SubmitHandler<SprintAccessFormValues> = (data) => {
    console.log("Murakkab validatsiyadan o'tgan ma'lumotlar:", data);
  };

  return (
    <form onSubmit={handleSubmit(onSubmit)} noValidate>
      {/* 1. Akkaunt turi */}
      <div>
        <label htmlFor="accountType">Akkaunt turi</label>
        <select
          id="accountType"
          {...register("accountType", {
            onChange: () => {
              // Akkaunt turi o'zgarganda bog'liq maydonni qayta tekshiramiz
              trigger("companyName");
            },
          })}
        >
          <option value="personal">Shaxsiy</option>
          <option value="business">Biznes</option>
        </select>
      </div>

      {/* 2. Shartli custom validation: faqat business bo'lsa majburiy */}
      <div style={{ marginTop: "1rem" }}>
        <label htmlFor="companyName">Kompaniya nomi</label>
        <input
          id="companyName"
          placeholder="Masalan: Dev-Bro LLC"
          {...register("companyName", {
            validate: (value, formValues) => {
              if (formValues.accountType === "business" && !value.trim()) {
                return "Biznes akkaunt uchun kompaniya nomi kiritilishi majburiy";
              }
              return true;
            },
          })}
        />
        {errors.companyName && (
          <p style={{ color: "red" }} role="alert">
            {errors.companyName.message}
          </p>
        )}
      </div>

      {/* 3. Boshlanish sanasi */}
      <div style={{ marginTop: "1rem" }}>
        <label htmlFor="startDate">Boshlanish sanasi</label>
        <input
          id="startDate"
          type="date"
          {...register("startDate", {
            required: "Boshlanish sanasini tanlang",
            onChange: () => {
              // Boshlanish sanasi o'zgarganda tugash sanasi xatosini darhol yangilaymiz
              trigger("endDate");
            },
          })}
        />
        {errors.startDate && (
          <p style={{ color: "red" }} role="alert">
            {errors.startDate.message}
          </p>
        )}
      </div>

      {/* 4. Cross-field validation: endDate >= startDate */}
      <div style={{ marginTop: "1rem" }}>
        <label htmlFor="endDate">Tugash sanasi</label>
        <input
          id="endDate"
          type="date"
          {...register("endDate", {
            required: "Tugash sanasini tanlang",
            validate: (value, formValues) => {
              if (!formValues.startDate || !value) return true;
              return (
                value >= formValues.startDate ||
                "Tugash sanasi boshlanish sanasidan oldin bo'lmasligi kerak"
              );
            },
          })}
        />
        {errors.endDate && (
          <p style={{ color: "red" }} role="alert">
            {errors.endDate.message}
          </p>
        )}
      </div>

      {/* 5. Named rules obyekti bilan bir nechta qoida */}
      <div style={{ marginTop: "1rem" }}>
        <label htmlFor="inviteCode">Taklif kodi</label>
        <input
          id="inviteCode"
          placeholder="Masalan: TEAM_2026"
          {...register("inviteCode", {
            required: "Taklif kodi majburiy",
            validate: {
              minChars: (value) =>
                value.trim().length >= 6 || "Kod kamida 6 belgidan iborat bo'lsin",
              upperAndDigit: (value) =>
                /^(?=.*[A-Z])(?=.*\d).+$/.test(value) ||
                "Kamida bitta katta harf va bitta raqam ishtirok etishi kerak",
            },
          })}
        />
        {errors.inviteCode && (
          <p style={{ color: "red" }} role="alert">
            {errors.inviteCode.message}{" "}
            <small style={{ color: "#888" }}>({errors.inviteCode.type})</small>
          </p>
        )}
      </div>

      <button
        type="submit"
        disabled={isSubmitting}
        style={{ marginTop: "1.25rem" }}
      >
        Tasdiqlash
      </button>
    </form>
  );
}

3. Muhim amaliy tavsiyalar

1. Bog'liq maydon o'zgarganda trigger("fieldName") chaqirish

Cross-field mantiqlarda (masalan, startDate va endDate): foydalanuvchi endDate ni to'g'ri kiritgan bo'lsa ham, keyinroq qaytib startDate ni kattaroq qilib o'zgartirsa, endDate avtomatik xatoga tushishi kerak. Bunga erishish uchun startDate dagi onChange hodisasida trigger("endDate") chaqirish kifoya.

2. Funksiyalarni alohida helper qilib ajratish

Agar validatsiya mantiqi juda murakkab bo'lsa (masalan: bank hisob raqamini modulli tekshirish, INN/STIR nazorat sonlarini hisoblash), bu mantiqni komponentdan tashqarida alohida validateCompany yoki validateDateRange helper funksiyalariga ajratish kodni toza va Unit-testlar uchun qulay qiladi.