Comment by Denny Trebbin on "Ask anything to MobX"

Denny Trebbin

Lead Fullstack Developer. Experimenting with bleeding-edge tech. Irregularly DJ. Hobby drone pilot. Amateur photographer.

May 10, 2016

I struggle with React-Router and its nested routes concept. That's why I put visibility logic of dump components into smart components. URLs can contain some app state too. To me, it's difficult to maintain state in Routes and Stores. On MobX docu router is only mentioned but never shown.

What do you think about UI Routing? Is it time to move on and keep all the state where it belongs to, in a state machine/state manager like MobX/Redux?

Michel Weststrate

JS / TS fanatic. Creator of MobX

May 10, 2016

For routing I try to resolve it somewhere in the root of the component tree, and just use it to update the view state of the application (like what is the current selection, or even page, etc). Then the rest of your application can become router unaware.

For updating the current url I always do one of the following:

just update it as part of your action, completely unrelated to mobx (for example when hitting a "login" button or something like that).
do it as side effect of a state change in an autorun, for example if the selection changes, see for example: github.com/mweststrate/mobx-contacts-list/blob/ma…

Denny Trebbin

Lead Fullstack Developer. Experimenting with bleeding-edge tech. Irregularly DJ. Hobby drone pilot. Amateur photographer.

May 10, 2016

No router. Great! :-)

Michel Weststrate

JS / TS fanatic. Creator of MobX

May 10, 2016

yeah that was an experiment. actually routers don't do that much it seems in modern browsers :-D

Search Hashnode