core: Reactivity regression in 3.14.15
Vue version
3.14.15
Link to minimal reproduction
Steps to reproduce
- Run the link
What is expected?
Input should show temp2.value: yes because item.v.value is updated which should trigger temp2, test and the watcher.
What is actually happening?
Input shows temp2.value: no
System Info
No response
Any additional comments?
In vue 3.14.12 a similar problem was introduced, which was fixed in 3.14.13. Then in 3.14.15 the same problem was re-introduced but for a more narrow edge case. Faulty commit: https://github.com/vuejs/core/commit/c2b274a887f61deb7e0185d1bef3b77d31e991cc
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Reactions: 1
- Comments: 15 (15 by maintainers)
Commits related to this issue
- fix(reactivity): handle `MaybeDirty` recurse (#10187) close #10185 — committed to vuejs/core by johnsoncodehk 5 months ago
It should be fixed by #10187. It would be helpful if you could provide a minimal test case.
Thanks @Doctor-wu
You made me realize that this is an anti-pattern in my code. But it would be nice if we could support recursive triggering and fix this one.
The reactivity refactoring in 3.4 could actually work in favor of this. If a computed retriggers itself we now have the chance to immediately re-evaluate as part of the value getter, before even triggering deps! Of course we needto watch out for infinite recursion and console.warn in case it happens…
Thanks but I think that the refered issue (and explanation) refers to returning an object.
testreturned value changes from"no"to"yes", which are both primitive values.I think that this is a regression caused by multiple levels of reactivity and tracking/triggering from within the same computed. Note that this worked up to version 3.4.14.
As a sidenote, I implemented a good part of the original reactivity system before the 3.4 refactoring.