If you were using an older version of angular CLI before it had aot built into it then you may start to receive these errors when you run you usual `ng serve` or `ng build` commands:
ERROR in Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 7:3 in the original .ts file), resolving symbol mainStoreReducer in /.../, resolving symbol AppModule in /../, resolving symbol AppModule in /../, resolving symbol AppModule in /../
If you've taken a look at some open source projects that use Ngrx such as example-app, ngrx-examples , or angular-nye-advanced-ngrx then you may have noticed that they have an interesting way of defining Action types. In this post I'll go over why we use the "type" method and why we construct the Action strings in this specific style. Big thanks to Xavier, @xlozingues, for staying at the office late on a Friday to help me understand this. ?
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.
The posts on this site are written and maintained by Jim Lynch. About Jim...