Add connectRouter + example

[dictions]

Fixes #1

[supasate]

Add trailing comma to pass eslint.

count: counterReducer,

[supasate]

Need to modify ConnectedRouter.js also

[supasate]

@dictions Need another little linting fix about trailing comma (#7 (review))

[dictions]

@supasate weird, I couldn't get eslint to fail with or without the trailing comma.

[supasate]

Oh, I just noticed that I don't use airbnb rules in this project. My eyes worked like airbnb linting compiler lol.

[supasate]

LGTM. Thank you for your contribution!

[dictions]

Of course! Mind bumping the version on merge?

[supasate]

Yes. I'll add some more details in the README before bumping version.

[supasate]

Already released in v2.0.0-alpha.1 https://github.com/supasate/connected-react-router/releases

[wtgtybhertgeghgtwtg]

Why is it a higher-order reducer?

[supasate]

@wtgtybhertgeghgtwtg To initialize router state with current browser history. Additional benefit is users don't have to mount router reducer themselves coz it's automatically mounted.

[wtgtybhertgeghgtwtg]

It complicates replaceReducer.

const newReducer = combineReducers(reducers);
store.replaceReducer(newReducer);

would have to be replaced with

const newReducerWithoutRouting = combineReducers(reducers);
const newReducer = connectReducer(history)(newReducerWithoutRouting);
store.replaceReducer(newReducer);

or, if you stored the result of the original connectReducer(history)

const newReducerWithoutRouting = combineReducers(reducers);
const newReducer = storedConnectReducer(newReducerWithoutRouting);
store.replaceReducer(newReducer);

[supasate]

I see your point about replacing reducer. Without higher order reducer, we've ever tried with following methods.

1. Dispatching onLocationChanged in constructor of ConnectedRouter with the current history location.
   However, the initial rendered page will be the default state before transitioning to the page of current history location. Therefore, we need somehow to set initial reducer state with values in history object.

2. We initially had an idea about creating a reducer creator that takes history object. Then, users call that creator and mount it to the root reducer.
   However, we found it complicated when most users separate the root reducer to another file and need to make a root-reducer creator to take history object in.

3. Our next solution is to import history directly in our router reducer file to create initial state. However, that makes it hard to test because it's highly coupled with history object.

4. We've reached the current solution to solve above issues by using higher order reducer.

(see our discussion here)

Therefore, I think, currently, I choose to trade-off with a bit complication of replacing reducer until we find a better solution. If you have any idea, please let me know.