Series: Axios Lesson 99

Axios in React — React loyihasida Axios'ni to'g'ri tashkil qilish

React loyihalarida Axios arxitekturasi: modulli papkalar tuzilishi (Client, Service, Hook, Component), Service Layer yaratish, unmount memory leaklardan saqlanish va TanStack Query integratsiyasi.

99-dars

Axios in React — React loyihasida Axios'ni to'g'ri tashkil qilish

Ko'plab boshlang'ich va o'rta darajadagi React loyihalarida eng ko'p uchraydigan arxitekturaviy xatolardan biri — bu har bir komponent ichida to'g'ridan-to'g'ri axios.get() yoki axios.post() chaqiruvlarini aralashtirib yuborishdir.

Bunday betartib yondashuv quyidagi jiddiy muammolarni keltirib chiqaradi:

  1. Kodni takrorlanishi (DRY buzilishi): Bir xil URL va parametrlar o'nlab komponentlarda qayta yoziladi.
  2. Kuchsiz bog'lanish (Tight Coupling): UI komponentlar bevosita tarmoq kutubxonasiga bog'lanib qoladi (ertaga Axios o'rniga boshqa narsa qo'yish yoki endpointni o'zgartirish butun ilovani buzadi).
  3. Testlashning qiyinligi: UI komponentlarni unit test qilishda tarmoq global obyektlarini mock qilish juda murakkablashadi.

Professional frontend arxitekturada (ayniqsa React, Vite va TypeScript muhitida) API qatlami aniq 3 ta bosqichga (Layer) ajratiladi: Client Config Layer, Service Layer va Component / Hook Layer.


1. Loyihada Papkalar Tuzilishi (Layered Architecture)

Katta hajmli va uzoq yashovchan loyihalarda kodni quyidagi modulli tuzilish asosida tashkil qilish eng maqbul standart hisoblanadi:

src/
├── api/
│   ├── client.ts         # Asosiy Axios instansiyasi, bazaviy sozlamalar va interceptorlar
│   ├── endpoints.ts      # API marshrutlari (URL) konstantalari
│   └── errorHandlers.ts  # Markazlashgan xatoliklarni xabar qilish (Toast/Alert)
├── services/
│   ├── auth.service.ts   # Autentifikatsiyaga oid metodlar (login, logout, refresh)
│   └── user.service.ts   # Foydalanuvchiga oid so'rovlar (getProfile, update)
├── hooks/
│   ├── useUser.ts        # React state va Service metodlarini bog'lovchi Custom Hooklar
│   └── useAuth.ts
└── components/
    └── UserProfile.tsx   # Faqat ma'lumotni chizishga (render) mas'ul toza UI
flowchart TD
    UI["UI Komponent\n(UserProfileComponent.tsx)"] --> Hook["Custom Hook\n(useUser.ts)"]
    Hook --> Service["Service Layer\n(user.service.ts)"]
    Service --> Client["Axios Client Layer\n(api/client.ts)"]
    Client --> Backend["Backend API Server"]

2. Service Layer — API So'rovlarini Markazlashtirish

Komponentlar hech qachon qaysi HTTP metodi (GET, POST) ishlatilayotganini yoki URL qayerdaligini bilishi shart emas. Har bir entity (foydalanuvchi, mahsulot, buyurtma) uchun alohida Service moduli yaratiladi:

// src/services/user.service.ts
import { apiClient } from '../api/client';

export interface UserProfile {
  id: string;
  fullName: string;
  email: string;
  role: string;
  avatarUrl?: string;
}

export interface UpdateUserPayload {
  fullName?: string;
  email?: string;
}

export const UserService = {
  /**
   * Foydalanuvchi profilini olish (AbortSignal qo'llab-quvvatlaydi)
   */
  getProfile: async (signal?: AbortSignal): Promise<UserProfile> => {
    const response = await apiClient.get<UserProfile>('/users/me', { signal });
    return response.data;
  },

  /**
   * Foydalanuvchi ma'lumotlarini qisman yangilash
   */
  updateProfile: async (
    payload: UpdateUserPayload,
    signal?: AbortSignal
  ): Promise<UserProfile> => {
    const response = await apiClient.patch<UserProfile>('/users/me', payload, {
      signal,
    });
    return response.data;
  },
};

3. React Komponentida Ishlatish (AbortController Bilan)

Komponent ichida so'rov yuborilganda foydalanuvchi sahifadan chiqib ketsa (component unmount), xotira sizib chiqishi (memory leak) yoki keraksiz tarmoq yuklamasining oldini olish uchun AbortController bilan toza yopish zarur:

// src/components/UserProfileComponent.tsx
import React, { useEffect, useState } from 'react';
import axios from 'axios';
import { UserService, UserProfile } from '../services/user.service';

export const UserProfileComponent: React.FC = () => {
  const [user, setUser] = useState<UserProfile | null>(null);
  const [loading, setLoading] = useState<boolean>(true);
  const [error, setError] = useState<string | null>(null);

  useEffect(() => {
    // 1. Yangi AbortController yaratamiz
    const abortController = new AbortController();

    const fetchUserData = async () => {
      try {
        setLoading(true);
        setError(null);

        // Servis metodiga abort signali uzatiladi
        const data = await UserService.getProfile(abortController.signal);
        setUser(data);
      } catch (err: unknown) {
        // Agar so'rov unmount tufayli bekor qilingan bo'lsa, xato ko'rsatmaymiz
        if (!axios.isCancel(err)) {
          if (err instanceof Error) {
            setError(err.message);
          } else {
            setError('Maʼlumotni yuklashda kutilmagan xatolik yuz berdi');
          }
        }
      } finally {
        setLoading(false);
      }
    };

    fetchUserData();

    // 2. Komponent ekrandan yo'qolganda so'rovni jismonan to'xtatamiz
    return () => {
      abortController.abort();
    };
  }, []);

  if (loading) return <div>Yuklanmoqda...</div>;
  if (error) return <div style={{ color: 'red' }}>Xatolik: {error}</div>;
  if (!user) return <div>Foydalanuvchi topilmadi.</div>;

  return (
    <div style={{ padding: '20px', border: '1px solid #ddd', borderRadius: '8px' }}>
      <h2>Foydalanuvchi Profili</h2>
      <p><strong>Ism:</strong> {user.fullName}</p>
      <p><strong>Email:</strong> {user.email}</p>
      <p><strong>Rol:</strong> {user.role}</p>
    </div>
  );
};

4. Zamonaviy Standart: TanStack Query (React Query) Bilan Integratsiya

Real loyihalarda useEffect, useState, loading va error holatlarini har safar qo'lda yozish o'rniga, yaratilgan UserService metodlarini TanStack Query bilan birlashtirish sanoatning eng zamonaviy standartidir:

// src/hooks/useUserProfile.ts
import { useQuery } from '@tanstack/react-query';
import { UserService } from '../services/user.service';

export const useUserProfile = () => {
  return useQuery({
    queryKey: ['user', 'profile'],
    queryFn: ({ signal }) => UserService.getProfile(signal),
    staleTime: 5 * 60 * 1000, // 5 daqiqa keshda saqlanadi
    retry: 2,                 // Xatoda 2 marta qayta urinish
  });
};

Komponentdagi natija esa bir qatorga qisqaradi:

export const CleanUserProfile: React.FC = () => {
  const { data: user, isLoading, isError, error } = useUserProfile();

  if (isLoading) return <div>Yuklanmoqda...</div>;
  if (isError) return <div>Xato yuz berdi: {(error as Error).message}</div>;

  return <div>Salom, {user?.fullName}!</div>;
};

5. Anti-Patterns vs Professional Yondashuv

Mezon ❌ Noto'g'ri (Anti-Pattern) ✅ To'g'ri (Professional)
So'rov joylashuvi Komponent ichida to'g'ridan-to'g'ri axios.get() Alohida src/services/ qatlamida
URL boshqaruvi Qattiq kodlangan (hardcoded strings) endpoints.ts yoki servis ichida markazlashgan
Unmount boshqaruvi Tekshirilmaydi (Memory leak) AbortController orqali toza bekor qilinadi
Tiplashtirish any ishlatiladi yoki tiplar yo'q TypeScript interfeyslari (UserProfile) bilan to'liq tiplashtirilgan
State boshqaruvi Har safar qo'lda loading/error Custom hooklar yoki TanStack Query orqali

Xulosa

React loyihalarida Axios'ni to'g'ri tashkil qilish — bu kod bazasining toza, kengaytiriluvchan va oson testlanuvchan bo'lishini ta'minlaydi.

  • client.ts — barcha global konfiguratsiya va interceptorlarni ushlab turadi;
  • services/ — biznes domenlari bo'yicha API chaqiruvlarini guruhlaydi;
  • UI komponentlar — faqatgina servis yoki hooklardan ma'lumot olib, sof render vazifasini bajaradi.