Router State === null & Nested object madness & Initial State

[igl]

Having the initial state of the redux-router-reducer generate null until the @routerDidChange action fires makes using the values in a mapStateToProps function rather ugly.

({router}) => ({
    searchTerm : router.location.query.term
})

has to be:

({router}) => ({
    searchTerm : router? (router.location? (router.location.query? router.location.query.term : '') : '' ) : ''
})

How can i avoid this?

[mikebarnhardt]

Would also like a resolution to this problem as mapStateToProps is being called twice on every page load due to @@reduxReactRouter/routerDidChange.

[Scarysize]

@MikeBarnhardt this was fixed by #183 @igl what would you prefer?

something like function routerStateReducer(state = { routes: [], params: null, location: null, components: [], }, action) {..}

[igl]

I use a custom store-enhancer now. I can't disable page transition in the dev-tools but all other headaches are gone and the simplicity of 45 lines vs redux-router is worth it.

[Scarysize]

@igi Great!

[igl]

https://gist.github.com/igl/23c8192a04b6251f3d60

[mikebarnhardt]

@Scarysize Thanks!