I recently wrote up an answer to this Stack Overflow question, and I was so proud of it that I decided to write up a blog post about it.
Yep, another blog post about Angular 2 and Ngrx. In this post we'll look at some ways to create @Effects that don't return an action to the reducer and when you might want to do this.
This post is meant to explain some of the magic behind the line of initialization code for Ngrx/Store that you put in the imports block of the NgModule. Working with provideStore is key to understanding how to setup your project wiht Ngrx, so let's get into it!
Here's an error I was having for the past few days that I'm a little embarrassed to admit. haha. As it t urns out the error was caused by me not returning anthing from a certain case of the swtich statement in my reducer function.
I've been working a lot recently with the Angular state management library ngr. I even wrote a blog post about setting up your Angular 2 project with ngrx/store and then a follow up post The Basics of"ngrx/effects", @Effect, and Async Middleware for "ngrx/store" in Angular 2. However, after taking a closer look at the official ngrx example project I learned a little trick that harnesses the power of TypeScript to make your coding experience even more fun and less error-prone.
The posts on this site are written and maintained by Jim Lynch. About Jim...