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

fix(runtime-core): ref in v-for does not trigger watchEffect #6169

Closed
wants to merge 2 commits into from

Conversation

liulinboyi
Copy link
Member

close #6168
fix(runtime-core): ref in v-for does not trigger watchEffect

@liulinboyi
Copy link
Member Author

Fix Preview

@WORMSS
Copy link

WORMSS commented Jun 26, 2022

Fix Preview

Beautiful.
I didn't know you could reference specific versions on the playground.
I look forward to this fixing a very similar problem we are seeing in our codebase..
(Fingers crossed they are related)..

@WORMSS
Copy link

WORMSS commented Jul 8, 2022

Can I ask what the hold up is for this PR? Maybe I can help unblock it?

@WORMSS
Copy link

WORMSS commented Jun 26, 2023

I see this is still not merged for some reason.. I was coming to see if there is anything I can do to help move this along?

@skirtles-code
Copy link
Contributor

I believe this same fix was merged in #6714, and was released in 3.2.41. The symptoms in the bug report for that PR were slightly different, but the fix ended up being the same.

@liulinboyi liulinboyi closed this Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Rejected
Development

Successfully merging this pull request may close these issues.

ref in v-for does not trigger watchEffect inside defineComponent
4 participants