Expose routerReducer so it works with @rematch/core about connected-react-router HOT 7 CLOSED

PR #140 is addressing this issue.

from connected-react-router.

Hey @linonetwo, I had a similar problem while using redux-sagas-injector. I needed the reducer exposed too, so I came up with a hack where you can get the reducer without exposing it from the library.

// pass the empty function for the rootReducer 
let routerReducer = connectRouter(history)(() => {}); 

// then use routerReducer as regular reducer in your reducers map with an extra line of code
let allMyReducers = {
...allMyReducers,
router: (state, action) => { let result = rootReducer(state, action); return state.router }
}

Let me know if it works for you, and please, let me know if I am missing something with this approach. Thanks!

from connected-react-router.

Sorry @dantonijevic , I'm not using connected-react-router and rematch anymore. I've switched to Apollo-GraphQL for more convenient data fetching...

from connected-react-router.

@linonetwo can you reopen this issue please? it's still relevant I think even though you're not using it anymore.

cc @supasate This would be really helpful to use with redux-loop

from connected-react-router.

bump @supasate any thoughts on this?

from connected-react-router.

cool thanks!

from connected-react-router.

Closing as already fixed in #150.

from connected-react-router.