Kif tiddeċidi fejn kull biċċa ta' stat għandha tkun?

Question

Accepted Answer

Deċiżjoni **fejn stat jibqa'** hija waħda mill-aktar ħiliet ta' arkitettura importanti. Il-prinċipju gwida: poġġi kull biċċa ta' stat fl-**iskop l-iktar strett** li għadu jissodisfa lil kulħadd li jeħtieġu — u tqabbel kull *tip* ta' stat mal-għodda t-tajba.

## Qafas ta' deċiżjoni

```text
1. Who needs this state?
   - One component                  → local state (useState)
   - A few related components        → lift to common parent / small context
   - Many distant components         → global store or context

2. What KIND of state is it?
   - Server/remote data              → server-state library (React Query/SWR)
   - UI/client state                 → useState / Zustand / Redux
   - URL-derivable (filters, page)    → the URL (searchParams)
   - Form input                       → form library or local state

3. How OFTEN does it change?
   - Rarely, widely shared (theme)    → Context is fine
   - Frequently, widely shared        → store with selective subscriptions
```

## Il-kategoriji u d-djar tagħhom

```text
State type     Lives in                       Examples
─────────────────────────────────────────────────────────────────
Local UI       component (useState)           input text, isOpen, hover
Shared UI      lifted parent / Context / store modal state, selected item
Server data    React Query / SWR / RTK Query  users, products (cached remote)
URL state      router / searchParams          filters, page, search query, tab
Form state     React Hook Form / local         field values, validation
Global app     Zustand / Redux / Context      auth user, theme, cart
```

## Żbalji komuni li l-qafas jipprevjeni

```text
❌ Server data in Redux       → use React Query (it's a cache, not UI state)
❌ Everything global "just in case" → over-coupling, extra re-renders; keep local
❌ Filters/page in state       → put in the URL (shareable, bookmarkable, back-button)
❌ Duplicating derivable values → derive instead (single source of truth)
❌ Form state in a global store → usually overkill; keep local or use a form lib
```

## L-URL hija stat użat b'mod insuffiċjenti

```text
Filters, pagination, search, active tab → belong in the URL.
Benefits: shareable links, browser back/forward works, survives refresh, SEO.
```

## Għaliex huwa importanti

Fejn stat jibqa' jiddetermina s-semplicità, il-prestazzjoni, u l-manutentibilità ta' app.

L-ħila hija li tqum kontra l-impuls li tagħmel kollox globali u minflok **tlokkalizza b'default, tqabbel kull tip ta' stat mal-għodda t-tajba tagħha** (data tal-server → React Query, derivabbli mill-URL → l-URL, UI → lokali/store).

Il-kisba ta' dan b'mod korrett tevita l-aktar problemi arkitetturali komuni — data tal-server midfuna f'Redux, stat globalizat żejjed li jikkawża re-render, u filtri fi stat tal-komponent minflok l-URL.

Din id-deċiżjoni hija dik li tissoċċja arkitettura ta' stat nadifa u skalabbli minn waħda mtewwla.