Its used as an optimization step for store slices selection. For example, if you return some heavy computation result for some store slice, then using createSelector will do memoization which means it will keep track of last input params to selector and if they are the same as current ones, it will return last result … Read more
The answer for the navigation scenario is your b answer @Effect navigateHome$: any = this.updates$ .whenAction(LoginActions.LOGIN_SUCCEEDED) .do(this.router.navigate(‘/home’)) .ignoreElements(); Explanation: You react to the LOGIN_SUCCESS, and because the router doesn’t return a new action, we need to stop the propagation of the stream, which we do by filtering everything. If you forget to filter, the router … Read more
The @ngrx/router-store exists so that it’s possible for the store to be the single source of truth for an application’s routing state. Without it, there would be application state – the current route – not represented in the store. That means time-travel debugging using the DevTools would not be possible, as there would be no … Read more