Platform: Example app doesn't use a Router as a single point of truth
Please change the example.
alvipeo
All 4 comments
Care to ellaborate?
brandonroberts
on 11 Sep 2017
Probably referring to https://blog.nrwl.io/using-ngrx-4-to-manage-state-in-angular-applications-64e7a1f84b7b
Router as the Source of Truth
There are many ways to approach the synchronization of the @ngrx/Store and the router. One way is to build a generic library synchronizing the store with the router. It won鈥檛 solve all of the problems, but at least the synchronization won鈥檛 be ad-hoc. Another way is to make navigation part of updating the store. And finally we can make updating the store part of navigation. Which one should we pick?
tja4472
on 11 Sep 2017
The example app uses the router as a single source of truth for navigation already with router-store. Closing as non-actionable
brandonroberts
on 11 Sep 2017
ok, so in this example you use router in the container component. Now, this container component only purpose is to make router a single point of truth. I think the whole idea of making a component as a link between app and router is not right. I like the nrwl approach better - it's just an effect and there you just dispatch appropriate action.
Components are for different purposes, well, to me.
I acknowledge that I can be wrong here. So, just IMHO.
alvipeo
on 11 Sep 2017
Related issues
dollyshah-02-zz
路
3Comments
doender
路
3Comments
smorandi
路
3Comments
gperdomor
路
3Comments
ghost
路
3Comments
Most helpful comment
ok, so in this example you use router in the container component. Now, this container component only purpose is to make router a single point of truth. I think the whole idea of making a component as a link between app and router is not right. I like the nrwl approach better - it's just an effect and there you just dispatch appropriate action.
Components are for different purposes, well, to me.
I acknowledge that I can be wrong here. So, just IMHO.