I figured it out! There was code in a component that was calling router.navigate() on a NavigationEnd event. So the answer was similar to the answer in this S.O. issue (rapidly changing the route). I got this error because I was calling router.navigate twice in quick succession, (1 to append queryParams, 1 to append a … Read more
In very simple terms select gives you back a slice of data from the application state wrapped into an Observable. What it means is, select operator gets the chunk of data you need and then it converts it into an Observable object. So, what you get back is an Observable that wraps the required data. … Read more
Quick version comment out createEffect(() =>, fix errors that your IDE (VSCode) flags up, add createEffect(() => back in. Alternative – rewriting like the following also works someEffect$ = createEffect(() => { return this.actions$.pipe( … ) }) Additional Still errors after doing the above? Type-checking is doing it’s job correctly and telling you that you … Read more
Try creating a copy of the array before trying to sort it. Like using a spread operator. arrayForSort = […this.taskList] Then after sorting you could assign it back to the taskList field
This worked for me nx test –test-file example.spec.ts
The topic is too wide. It will be like a tutorial. I will give it a try anyway. In a normal case, you will have an action, reducer and a store. Actions are dispatched by the store, which is subscribed to by the reducer. Then the reducer acts on the action, and forms a new … Read more
General information NGRX Router docs ngrx router is Deprecated! There is migration strategy from ngrx router to the standard Angular2 Router. Angular2 Router docs Default solution from Angular team Was inspired by UI-router from AngularJS Built for components Angular2 Router has almost all UI-router features. NG2 UI-router docs Well known UI-router from AngularJS updated for … Read more
@Effect() loadInitConfig$ = this.actions$ .ofType(layout.ActionTypes.LOAD_INIT_CONFIGURATION) .map<Action, void>(toPayload) .switchMap(() => this.settingsService .loadInitConfiguration() .mergeMap((data: any) => [ new layout.LoadInitConfigurationCompleteAction(data.settings), new meetup.LoadInitGeolocationCompleteAction(data.geolocation) ]) .catch(error => Observable.of( new layout.LoadInitConfigurationFailAction({ error }) ) ) );
Neither, you should compose your application as smart and presentation components. Advantages: All buissness logic on the smart controller. Just one subscribe Reusability The presentation controller has only one responsibility, only to present data and does not know from where the data come from. (loosely coupled) Answering the last question: The massive use of async … Read more
You can subscribe to actions in components as well: […] import { Actions } from ‘@ngrx/effects’; […] @Component(…) class SomeComponent implements OnDestroy { destroyed$ = new Subject<boolean>(); constructor(updates$: Actions) { updates$.pipe( ofType(PostActions.SAVE_POST_SUCCESS), takeUntil(this.destroyed$) ) .subscribe(() => { /* hooray, success, show notification alert etc.. */ }); } ngOnDestroy() { this.destroyed$.next(true); this.destroyed$.complete(); } }