-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
fix(reactivity): correct dirty assign in render function #10091
fix(reactivity): correct dirty assign in render function #10091
Conversation
Size ReportBundles
Usages
|
@johnsoncodehk Could you help to review this? First time to read the new reactivity system, not sure if it's totally ok, but it works to solve the issue and pass all tests |
this doesn't seem to fix that, this demo should work(works in 3.3). |
This demo seems to be another issue different from this one, maybe we should commit another issue? |
Whatever, I will take a look, mention me if you commit another issue~ |
Btw good job @Doctor-wu ! I was looking at this as well before dinner and also located the issue to be in |
@yyx990803 glad to help~ |
/ecosystem-ci run |
📝 Ran ecosystem CI: Open
|
Looks like this caused pretty serious regressions in Nuxt and Quasar, unfortunately the tests in core didn't really capture those complicated cases. |
It's a pity that it didn't really solve the problem. It is challenging to include numerous complex cases in the core tests. I believe it would be reasonable to allow the ecosystem to develop more complex cases. Perhaps we should run the ecosystem CI before merging |
close #10082