Thank you Victor for another insightful and thought provoking article.
Waldo ad Springe

This is a tricky subject because, yes, reducer functions should be pure (which is why ngrx/effects was created to handle side effects away from the reducer). On the other hand, Victor’s important point is that, since a main purpose of the router is to allow the use of deep links, and thus initiate the application at any arbitrary state specified in the URL, the router has to be the ultimate driver of state (at least to the extent of what he’s calling persistent client state). We are still pretty far from a consensus on best practices here, which is as it should be because this is all very new, considering the scale of the issues involved.

Like what you read? Give Robert Polevoi a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.