Good Action Hygiene with NgRx
summary
Claims that three concrete pitfalls wreck NgRx apps: reusing actions, generic action types, and action subtyping, and that fixing them raises quality and testability. Uses NgRx primitives—actions, reducers, effects—and Store DevTools to show how descriptive action types and writing actions first cut conditional branches, simplify effects, and make logs readable. Walks through a menu-ordering example (burgers, tacos) and reports that better actions let a new engineer, Sherry, ramp up quickly using the devtools.
AI-written summary · about
chapters (4)
related talks
35mAdvanced NgRx Techniques
30mState Management Patterns and Best Practices with NgRx
34mNgRx: Tips & Tricks
20mComplexity Management with NgRx
33m5 Tips to Improve User Experience with NgRx
01h 04mRedux for Angular -- Introduction to Ngrx Ecosystem
32mLevel up your NgRx game
27mWhy You Should Definitely Use NgRx