Event Driven Redux
summary
Shows concrete, testable patterns to shrink Redux boilerplate: use redux toolkit and its createAction/createReducer helpers plus Emer to write immutable updates imperatively, prefer actions as events (past‑tense events) so many reducers and sagas respond to a single dispatch, and start components in Storybook to drive prop design before wiring containers. Gives exact code‑level swaps and measurable wins — fewer actions, simpler containers, and easier tests.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:35Redux is not dead
- 3:32Background
- 5:34My Experience with Redux
- 8:05Redux Toolkit
- 11:44Redux Hooks
- 13:08Redux Architecture
- 15:54Components
- 17:24Actions
- 18:39Commands
- 20:01Reducers
- 22:01Action Events
- 23:54Modal Reducer
- 24:42PubSub Architecture
- 25:45Storybook Architecture
- 27:54Redux Style Guide
