How to Write Bad Code in Redux
summary
Redux does not guarantee a single source of truth and projects using it for dozens of apps discover real bugs from accidental mutations and deep cloning; development teams adopt redux-freeze and lodash/fp or immer to catch or avoid mutation, keep plain objects for serialization and TypeScript friendliness, derive views with reselect and separate server vs UI state, and implement an API middleware with labeled counters plus a single loading reducer — a concrete middleware plus boilerplate that proved reusable across many projects.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:20Who agrees with this
- 2:08Immutable data
- 3:08Shallow copy
- 4:42Redux Freeze
- 6:01Deep Cloning
- 7:03EEMA
- 7:53Reducers
- 8:25Selectors
- 10:37Single Source of Truth
- 12:50Selectors and Reducers
- 13:40Middleware
- 14:43State Design
- 17:02Code Reuse
- 19:39Boilerplate
- 20:56API middleware walkthrough
- 23:44Higherorder reducers
- 25:28Outro
