Reducing the Boilerplate with NgRx - Brandon Roberts & Mike Ryan
Why Stack Overflow recommends it
Stack Overflow users link it when asked how to keep NgRx code DRY or when to use the store at all, since it comes from the library's own authors.
Recommended by 2 people across 2 different months, 2018 to 2020.
What it is
A ng-conf 2018 conference talk by NgRx maintainers Brandon Roberts and Mike Ryan on cutting down the repetitive code that comes with using NgRx (Redux-style state management) in Angular apps. It covers patterns and helpers that make actions, reducers and effects less verbose.
What people said
Recommends Vash72 · 2018-09 · Stack Overflow · on “How to keep ngrx DRY?”
No , this is ngrx(redux) famous "boilerplate" but watch the author of ngrx giving some good hints about Reducing the Boilerplate with NgRx - Brandon Roberts & Mike Ryan [this video]
Recommends timdeschryver · 2019-10 · Stack Overflow · on “How best to use Reactive State?”
Without knowing the use case it's hard to give a correct answer to this question, because it all depends on the needs. As a rule of thumb, if the state only affects the current component, the ngrx store is not the place to store its data. An example of this is a form, it's usually an overkill to sync the form with the state in the store. That being said, if you need rehydration on the form, it's a good use case to keep the form and the store in sync. The minus of dispatching a lot of actions, isn't a "real" downside of it imho - the ngrx store (redux in general) is designed to handle a lot of incoming actions. To answer the second question, yes that's were reducers are for imho - it's here w
Cites andriishupta · 2020-02 · Stack Overflow · on “Ngrx pattern for dispatching action and checking if backend call was successful”
This is an ngrx's flow. Also, you could simply call some alert if there is no hard logic to do for views. And to mention - you don't need to always use ngrx(from creators of ngrx) - [this video]