Apa sing diwenehake Redux Toolkit (RTK) tinimbang Redux klasik?

Question

Accepted Answer

**Redux Toolkit (RTK)** minangka cara resmi lan disaranake kanggo nulis Redux saiki. Ngilangake boilerplate sing misuwur saka Redux klasik — tipe aksi manual, pembuat aksi, logika pembaruan immutable, setup toko — nanging tetep ngetrapake prinsip inti sing padha.

## Masalah boilerplate sing dipecahake RTK

```js
// ❌ classic Redux — verbose: action types, creators, switch reducers, manual immutability
const INCREMENT = "counter/increment";
const increment = () => ({ type: INCREMENT });
function reducer(state = { value: 0 }, action) {
  switch (action.type) {
    case INCREMENT: return { ...state, value: state.value + 1 };
    default: return state;
  }
}
```

## RTK: createSlice nggawé kabeh

```js
import { createSlice, configureStore } from "@reduxjs/toolkit";

export const { increment, incrementBy } = counterSlice.actions; // action creators AUTO-generated
const store = configureStore({ reducer: { counter: counterSlice.reducer } });
```

`createSlice` nghasilake tipe aksi lan pembuat kanthi otomatis, lan — liwat **Immer** — ngidini kowe nulis kode reducer "mutating" sing aman diubah dadi pembaruan immutable. Siji slice sing ringkas ngganti kabeh bagian manual.

## Apa maneh sing kalebu RTK

```text
configureStore   → store setup with DevTools + thunk middleware preconfigured
createAsyncThunk → standard async (pending/fulfilled/rejected actions) for data fetching
createEntityAdapter → normalized state + CRUD reducers for collections
RTK Query        → a full data-fetching/caching layer (like React Query, built into Redux)
```

## Conto createAsyncThunk

```js
export const fetchUsers = createAsyncThunk("users/fetch", () => api.getUsers());
// auto-dispatches users/fetch/pending | fulfilled | rejected — handle in extraReducers
```

## Mengapa RTK dadi standar saiki

```text
✓ ~75% less code than classic Redux
✓ Immer → no manual immutable spread logic (fewer bugs)
✓ Good defaults (DevTools, thunk) out of the box
✓ Encourages best practices (slices, normalized data)
✓ RTK Query bundles server-state management
```

## Mengapa iku penting

Kritik paling gedhe saka Redux klasik yaiku boilerplate-ne; RTK langsung nyepak masalah iki, mula iku saiki dadi **rekomendasi resmi** lan apa teges "nggunakake Redux" ing codebase modern.

Nangerteni `createSlice` (kapanggihake Immer, aksi sing dibuat kanthi otomatis), `createAsyncThunk` (asinkron), `createEntityAdapter` (normalisasi), lan RTK Query (negara server) iku penting kanggo kerja Redux kontemporer — mumet prediktabilitas Redux nalika ngilangi seremonial sing nyurung pirang-pirang tim menyang alternatif.