Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Navigating to a default route hands off responsibility to the history adapters which use the appropriate mechanism, when using the HashHistory this uses the hashchange event which is asynchronous.
When calling the router instance's setPath() explicitly we should synchronously process the change and guard against repeated (surplus) processing in the adaptors.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.