-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Watchers leaked when component destroyed #599
Comments
I'd say that this is expected behavior because Vuex cannot detect in which component you call /ping @yyx990803 |
In its current state, it can't detect it, but I believe it would be possible to override the watch method in each components |
I don't think we can override the |
|
It seems that when a component watches anything in a $store, the watchers stick around once the component has been destroyed. I'm curious if it wouldn't be better to track watches per-component (in the Vuex mixin) and remove them once the component is destroyed.
Relevant fiddle: http://jsfiddle.net/thatguystone/zz727dhb/
The text was updated successfully, but these errors were encountered: