ngrx-router-store

Navigation ID is not equal to the current router navigation id error

蹲街弑〆低调 提交于 2020-01-03 06:48:11
问题 I'm using @ngrx/router-store in my Angularv5 app and I recently started running into a an error: Navigation ID X is not equal to the current navigation id Y (where X and Y are integers). This problem happens consistently when I navigate to route A from a specific route B. Navigating to route A from any other route seems to work fine. The only other S.O. issue related to this which I've found, offers up the possibility that the issue could be caused by rapidly updating the navigation multiple

angular and error of attempting to configure _source for RouterOutlet and NgIf

佐手、 提交于 2019-12-24 00:16:43
问题 I have an app where app.component only has router-outlet. I was having no issues until I added an ng-template for a ViewChild in a component 4 levels down from app component. here is the structure: AppComponent lazy loads FolderModule with FolderComponent. the folder component template is an ngFor that renders child components. it is the child component that has the ViewChild. I am not sure of a good way to explain this. I think the ngIf in the error is my ng-if that loads the page once there

How to access Resolver Data in ngrx/effects? (v7)

自作多情 提交于 2019-12-13 04:25:20
问题 I have api calls in the component which is time taking , so i have implemented resolver. I want the resolver data to be present in the store , for later use. I have implemented ngrx/store, ngrx/effects and ngrx/router-store. Current state in component getting data directly from resolver data in component (route is of type ActivatedRoute) Desired state To keep the resolver data in store, I need to access resolver data in effects. So i can simply dispatch action in component and subscribe the