Allow passing custom History object #173
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This exposes a param on the router called
history
. By default, it will useglobalHistory
, but we can pass an API-compatible history object and it will be used instead. For example, we can force it to use a memory source (closes #153):I've also noticed that the History type is kinda like the history package used in React Router – apart from
navigate
vs.push
/replace
, it seems like a drop-in replacement. You might want to switch to that instead, as it seems like a good abstraction overall – but that's up to you :)