Version 2.7.15 introduced breaking changes about getCurrentScope
1593292349 opened this issue · 2 comments
1593292349 commented
Version
2.7.15
Reproduction link
Steps to reproduce
- npm install
2.npm run start
3.Execute the "getCurrentScope "method on the console
What is expected?
The getCurrentScope method returns undefined
What is actually happening?
The getCurrentScope method returns not undefined
The getCurrentScope method returns undefined in version 2.7.14
1593292349 commented
I traced this line of code to affect this behavior，I'm not sure it's a bug。
1593292349 commented
There is always an activeEffectScope，Causes watchEffect to bind to an incorrect instance and then be accidentally destroyed