-
-
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
reactivity issue with property watch and emit #2200
Comments
The data for "description" is correctly updated and the component even-re-renders - seems rather to be a bug in a vdom optimization? but then why do the other approaches correctly update the DOM? Weird. |
This probably related to recent changes in the watch mechanism defaults. Using watch: {
setit: {
handler: 'tellParent',
flush: 'post'
}
}, It's in the changelog |
But then the question remains why do we need to choose And if this is indeed a new behavior in Vue 3, then we need to properly document it. |
This looks like a re-occurrence of #1801. If you explicitly set |
So that the scheduler also respects effect's allowRecurse option. fix #2200
Version
3.0.0
Reproduction link
https://jsfiddle.net/unz2ga94/
Steps to reproduce
On the minimal reproduction example, click on "via watch on component property"
What is expected?
it should display "global: indirectVal"
What is actually happening?
it displays "global: initialValue"
On the minimal reproduction example, you can replace https://unpkg.com/vue@next with https://unpkg.com/vue@2.x to show the behaviour with Vue.js 2.x
Is this an expected regression? (I've read various migration stuff and didn't find any mention of this).
In the project that hit this issue, the component is doing stuff with textarea cursor: component code
The text was updated successfully, but these errors were encountered: