AxiosResponse — Response ma'lumotlarini generic orqali tipizatsiya qilish
AxiosResponse<T> interfeysi: generic orqali server javobini tipizatsiya qilish, CRUD amallarida qo'llash, Service Layer'da datani ajratib olish va any ishlatishdan qochish.
44-dars
AxiosResponse — Response ma'lumotlarini generic orqali tipizatsiya qilish
Serverga so'rov yuborganingizda, Axios har doim butun bir HTTP javob obyektini qaytaradi. TypeScript'da bu obyekt AxiosResponse interfeysi orqali ifodalanadi. Generik <T> belgisi esa aynan o'sha obyektning ichidagi data (asosiy ma'lumot) qismining aniq turini (tipini) belgilaydi.
1. AxiosResponse<T> qanday tuzilgan?
Axios kutubxonasining ichki TypeScript ta'riflariga qarasak, u taxminan quyidagicha tuzilganini ko'ramiz:
export interface AxiosResponse<T = any> {
data: T; // <T> aynan shu yerga, ya'ni asosiy javobga tushadi
status: number; // HTTP status kodi (masalan, 200, 201)
statusText: string; // Status matni (masalan, "OK")
headers: RawAxiosResponseHeaders | AxiosResponseHeaders; // Server sarlavhalari
config: InternalAxiosRequestConfig; // So'rov konfiguratsiyasi
request?: any; // Asl XMLHttpRequest yoki Node.js request obyekti
}
Agar siz apiClient.get<User>('/user/1') deb yozsangiz, TypeScript darhol tushunadiki: "Demak, response.data ning turi User interfeysiga teng ekan!".
2. Generik <T> ni amalda qo'llash (CRUD misolida)
Har xil HTTP metodlarida tiplashtirish bir xil qoidaga asoslanadi:
import { apiClient } from './client';
// 1. Turlarni (Interfaces) e'lon qilamiz
export interface Article {
id: number;
title: string;
body: string;
}
// 2. Olish (GET) - Odatda massiv yoki bitta obyekt qaytadi
export const fetchArticles = async () => {
// Javob AxiosResponse<Article[]> bo'ladi
const response = await apiClient.get<Article[]>('/articles');
// response.data ustiga sichqonchani olib borsangiz, TypeScript uni Article[] deb taniydi
return response.data;
};
// 3. Yaratish (POST) - Yangi yaratilgan obyekt qaytadi
export const createArticle = async (newArticle: Omit<Article, 'id'>) => {
const response = await apiClient.post<Article>('/articles', newArticle);
return response.data; // Tipi: Article
};
// 4. O'chirish (DELETE) - Ko'pincha server bo'sh yoki status qaytaradi
export const deleteArticle = async (id: number) => {
const response = await apiClient.delete<{ success: boolean }>(`/articles/${id}`);
return response.data;
};
3. Service Layer Arxitekturasida AxiosResponse<T> ni yashirish
Professional React va frontend loyihalarida UI komponentlari AxiosResponse nima ekanligini umuman bilmasligi kerak. Komponentga faqat sof ma'lumotning o'zi zarur. Shuning uchun Service qatlamida (API Service Layer) AxiosResponse obyekti "parchalanib", undan faqat data ajratib olinadi va qaytariladi.
Bunday yondashuvda servis funksiyasining qaytarish turi doimo Promise<T> bo'ladi:
// src/services/articleService.ts
import { apiClient } from '../api/client';
import { Article } from '../types';
export const ArticleService = {
// Funksiya Promise<Article[]> qaytarishini aniq yozib qo'yamiz
getAll: async (): Promise<Article[]> => {
// Bu yerda res obyekti AxiosResponse<Article[]> ekanligini TypeScript biladi
const res = await apiClient.get<Article[]>('/articles');
// Biz komponentga faqat sof ma'lumotni (data) uzatamiz
return res.data;
},
getById: async (id: number): Promise<Article> => {
const res = await apiClient.get<Article>(`/articles/${id}`);
return res.data;
}
};
Natijada UI komponentida kod juda sodda va toza bo'ladi:
// src/components/ArticleList.tsx
import React, { useEffect, useState } from 'react';
import { ArticleService } from '../services/articleService';
import { Article } from '../types';
export const ArticleList = () => {
const [articles, setArticles] = useState<Article[]>([]);
useEffect(() => {
const loadData = async () => {
// data to'g'ridan-to'g'ri Article[] bo'lib keladi,
// hech qanday data.data yozishga hojat yo'q!
const data = await ArticleService.getAll();
setArticles(data);
};
loadData();
}, []);
return (
<ul>
{articles.map((item) => (
<li key={item.id}>{item.title}</li>
))}
</ul>
);
};
4. Qat'iy qoida: any ishlatishdan qoching!
[!CAUTION] Agar siz
<T>ga hech qanday tip bermasangiz (apiClient.get('/users')), TypeScript uni sukut bo'yichaanydeb qabul qiladi. Bu esa TypeScript'ning barcha xavfsizlik, refaktoring va autocomplete imkoniyatlarini yo'qqa chiqaradi.
// ❌ YOMON AMALIYOT (Type-safety yo'qoladi):
const res = await apiClient.get('/articles');
res.data.nonExistentField.foo(); // Kompilyatsiyada xato bermaydi, lekin brauzerda qulaydi!
// ✅ YAXSHI AMALIYOT (To'liq xavfsiz):
const res = await apiClient.get<Article[]>('/articles');
res.data[0].title; // IDE avtomatik taklif beradi va xatolardan himoya qiladi
5. AxiosResponse bilan ishlash usullari taqqoslovi
| Yondashuv | Qayerda qo'llaniladi? | Natija | Afzalligi / Kamchiligi |
|---|---|---|---|
apiClient.get<T>() |
Service qatlamida | AxiosResponse<T> |
Status, headers va boshqa meta-ma'lumotlarni tekshirish imkoni bor |
return response.data |
Service metodlarida | Sof T ma'lumoti |
UI qatlami Axios'dan mustaqil bo'ladi, kod ancha toza |
| Interceptor orqali unwrap | Global response interceptor'da | Har bir so'rovda to'g'ridan-to'g'ri T |
res.data yozish umuman shart bo'lmaydi, biroq AxiosResponse strukturasini buzishi mumkin |
Xulosa
AxiosResponse<T> — serverdan keladigan javoblarni to'liq tiplashtirishning eng ishonchli vositasidir. Service qatlamida uni qabul qilib, UI komponentlariga faqat response.data ni uzatish frontend arxitekturasini qisqa, tushunarli va mustahkam qiladi.