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

Version 2.7.15 introduced breaking changes about getCurrentScope #13131

Closed
1593292349 opened this issue Dec 12, 2023 · 2 comments
Closed

Version 2.7.15 introduced breaking changes about getCurrentScope #13131

1593292349 opened this issue Dec 12, 2023 · 2 comments

Comments

@1593292349
Copy link

Version

2.7.15

Reproduction link

github.com

Steps to reproduce

  1. 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
Copy link
Author

image
I traced this line of code to affect this behavior,I'm not sure it's a bug。

@1593292349
Copy link
Author

There is always an activeEffectScope,Causes watchEffect to bind to an incorrect instance and then be accidentally destroyed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant