Reducing Redux Boilerplate
summary
Argues that Redux boilerplate falls by collocating behavior: actions carry the reducer function and an optional path so updates run deep in state, letting constants disappear and middleware still see a type. Shows an action factory that produces path-bound actions for many counters and demonstrates it on a simple counter example. Claims this reduces files and indirection, preserves Redux middleware compatibility, and sacrifices strict action serializability while working in practice.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:22Redux Example
- 0:42So what's wrong with that?
- 0:52Code spread across directories
- 1:08Reducers are not declarative
- 1:27Collocating action + its reducer
- 1:51Removing constants
- 2:28Adding Path
- 2:54More counters? No problem!
- 3:41What did we gain?
- 4:03What did we lose?
- 4:28Summary
