Structure Your App's Story With Sagas and Selectors
summary
Claims that selectors should contain data shaping (example: best‑selling authors filter), argues conditional checks belong in reducers not thunky action creators (example: conditional add‑to‑cart using a selector), and recommends redux-saga for complex async flows (examples: load‑books saga, onboarding saga, game logic centralized in sagas). Mentions reselect for memoization, keeps API calls in services, and reports that sagas make multi‑step process flow readable and reliably work in larger apps.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:29Asynchronous Data Flow
- 2:10Data Manipulation
- 3:30Conditional Business Logic
- 4:32Principles of Redux
- 4:49Benefits to Favoring Reducers
- 6:03Redux Saga
- 7:01File Structure
- 7:34Data Manipulation Business Logic
related talks
32mStructuring Your App’s Story With Sagas and Selectors
29mStructure Your App's Story With Sagas and Selectors
45mRedux and Redux-saga to manage states in a large React app
54mThe Saga of yield: Hidden Capabilities
41mRedux Saga, the Viking way to manage side effects
21mLet's Sync the Async- A Primer on Redux Sagas
30mMake React State-Management great again
36mReact + Redux: Performance & Scalability