Using combineReducers | Redux
redux.js.org · 973 words · saved by 1 readers
Structuring Reducers > Using combineReducers: Explanations of how combineReducers works in practice
On this page Core Concepts The most common state shape for a Redux app is a plain Javascript object containing "slices" of domain-specific data at each top-level key. Similarly, the most common approach to writing reducer logic for that state shape is to have "slice reducer" functions, each with the same (state, action) signature, and each responsible for managing all updates to that specific slice of state. Multiple slice reducers can respond to the same action, independently update their own slice as needed, and the updated slices are combined into the new state object. Because this patter
related reading
- Redux Essentials, Part 1: Redux Overview and Concepts | Reduxredux.js.org
- Extracting State Logic into a Reducer – Reactreact.dev
- A guide to the React useReducer Hook - LogRocket Blogblog.logrocket.com
- Redux Fundamentals, Part 1: Redux Overview | Reduxredux.js.org
- Frulow: Trending Products, Gadgets, Librariesapp.frulow.com
- Chloe's Gardenchloeyan.me
- Polymatheth-tokenstudio.polymath.network
- Tao of React - Software Design, Architecture & Best Practices | Alex Kondovalexkondov.com
- How to use Zustand | Refinerefine.dev
- You Might Not Need an Effect – Reactreact.dev
- SWR: React Hooks for Data Fetching - Vercelswr.vercel.app
- A data race that doesn't compilecorentin-core.github.io