From Inactive to Reactive with ngrx
summary
A simple book‑search app gets reworked into a predictable reactive system: UI events become actions, state lives in ngrx store, HTTP requests move into ngrx effects and return search‑success actions, components subscribe via selectors and use OnPush change detection, and the Redux DevTools time‑travels state for debugging. Code shown: action classes, a reducer, selectors, an effect using switchMap, module wiring and removal of HTTP from components so the UI is pure.
AI-written summary · about
chapters (11)
- 0:00Intro
- 4:09Model Actions
- 8:36Search Reducer
- 20:25Selectors
- 23:00Recap
- 24:48Indirect Effects
- 26:10Side Effects
- 30:27Recap Effects
- 31:33Refactoring
- 33:08Redux Dev Tools
- 36:56Wrap Up
related talks
34mReactive State Management For Your Angular App
23mState management with ngrx
44mAngular + Redux ... stop, what?
38mThe Hitchhiker' s Guide To NGRX
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem
27mngRx the last piece in the Angular architecture puzzle
01h 00mReactive Programming, State Management, and Redux for the Modern Front End Dev
22mState Management Techniques and Family Therapy