-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
throw Cannot read properties of undefined (reading 'stop')
on component unmount, and use nested watch.
#5783
Comments
I don't think you are supposed to call the |
Yes, there are many other ways. But in my project, I want to do is when a property (e.g. So, "naturally" I use nested watch. (There may be other, more natural and better ways, which I don't know of.) Also, since this is an unreasonable way and it does cause an error, is there any way to stop people using it? |
You can use the solution I showed you at the moment. I don't know if it makes sense to activate the watcher effectScope within a running watcher |
@posva @LinusBorg |
…ve scope close vuejs#5783 close vuejs#5806
Version
3.2.30
Reproduction link
sfc.vuejs.org/
Steps to reproduce
What is expected?
When the 'Toggle' button is clicked, the
<Comp>
component is unmounted normally.What is actually happening?
'Toggle' button then change
visible
tofalse
, then it will cause the<Comp>
to be unmount, and throw error.The issue is present in 3.2.30 and later.
The text was updated successfully, but these errors were encountered: