How to decouple state and UI (a.k.a. you don’t need componentWillMount)
Michel Weststrate
2.5K24

Awesome concept! Have been using it in Sulu for quite some time now, and it works pretty well. However, there is a new requirement coming in, about which I am not sure how to solve it.

We’d like to be able to navigate the route, without adding an entry to the browser history. That would be super useful for redirects, because if we’ll create a history entry for them, the back button will immediately land you on the current page again, which makes it pretty useless…

How would you tackle that problem? It boils down to using replaceState instead of pushState in the autorun, but how do I know which one to use? Thought about setting a flag before the autorun is called and reset it after having decided if pushState or replaceState should be called, but I’ve got the feeling that might have other unwanted side effects…