-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
feat(history): Reset history.current when all apps are destroyed #3298
Conversation
@posva @joeldenning look at the PR, please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, left a few comments.
@@ -252,11 +252,17 @@ export class History { | |||
// Default implementation is empty | |||
} | |||
|
|||
teardownListeners () { | |||
teardown () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we rename this method, it might make sense to rename the setupListeners
method, too.
vue-router/src/history/base.js
Line 251 in dfc2892
setupListeners () { |
src/history/base.js
Outdated
this.pending = null | ||
} | ||
|
||
teardown () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can just put everything inside here as I don't think it makes sense to call teardownListeners
or resetHistoryState
separately
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@posva done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Thank you for your effort of supporting and developing vue :) |
This resolves #3294