Skip to content
New issue

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? Sign in to your account

Routing: Navigation to default route should be syncronous #145

Closed
agubler opened this issue Oct 25, 2018 · 0 comments · Fixed by #148

Comments

@agubler
Copy link
Member

commented Oct 25, 2018

Bug

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.

@agubler agubler added the bug label Oct 25, 2018

@agubler agubler referenced this issue Oct 25, 2018
3 of 3 tasks complete

@agubler agubler closed this in #148 Oct 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.