Navada za ka yanke shawarar inda kowane gunin state ya kamata ya zauna?

Question

Accepted Answer

Yanke shawarar **inda state ya zauna** yana da mahimmanci sosai a cikin sana'ar gida. Saurin jagoranci: sanya kowane gunin state a cikin **mafi ƙaramin scope** wanda har yanzu ke cika bukatun kowa da ke bukatunsa — kuma daidaita kowane *nau'i* na state zuwa kayan aiki daidai.

## Tsarin yanke shawarar

```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
```

## Categories da wuraren su

```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
```

## Kurakuran gida da tsarin ke kawar da su

```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
```

## URL yana kashe matakin state

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

## Me ya sa wannan yana da mahimmanci

Inda state ya zauna yana ƙayyade sauƙi na app, aiki, da sauken lura.

Sashen fasaha yana ma komawa buƙatun yin kome mahadi kuma a madaidaiciya **kashe jihin gida ta tsohuwa, daidaita kowane nau'i na state zuwa kayan aiki daidai** (bayanan sabuwa → React Query, URL-abubuwan da za a iya samun → URL, UI → gida/ajiye).

Samuwa daidai haka yana kawar da matsaloli masu yawa na gida — bayanan sabuwa wanda aka cinka a cikin Redux, state da aka ɓata jiya kan cikawa yana haifar da sake fuskantarwa, kuma matanin da suke cikin state na abin da aka yi ba a URL ba.

Judgment ga wannan shi ne abin da ke raba tsarin state gida mai sauƙi mai sauƙi daga wanda ba a bugi.