Allow to pass config with history

[cursedcoder]

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

This introduces config to react3 router, so tests now can be run using any external history.

[coveralls]

Coverage increased (+0.06%) to 97.189% when pulling 0ae27d3 on cursedcoder:feature/react-router-config into 4bb126c on trialspark:master.

[minznerjosh]

Thanks for the PR! Can you provide some more context on your use-case for this feature? Why is the MemoryHistory that the react-router plugin creates for you not working?

[cursedcoder]

I want to test the whole application without changing any components it uses.
In my case replacing hashHistory with memoryHistory introduces different behavior during testing.

Take aside my case, you can see this code looks like it is doing too much under the hood without external input. I think package users should have a little bit more control over that.

[cursedcoder]

For anyone curious about workaround, here is a snippet without typescript https://gist.github.com/cursedcoder/a222884a8e13ec3c66ff82857ec171bf

[cursedcoder]

@minznerjosh any news?

[minznerjosh]

Sorry for the ridiculous delay! Let's ship this! Can you just update the docs to include this new configuration option?