Questions about "dx: warn users when computed is self-triggering" #10340
Unanswered
SirH3nry
asked this question in
Help/Questions
Replies: 2 comments 3 replies
-
A minimal reproduction will be great, a repo will be OK as well |
Beta Was this translation helpful? Give feedback.
3 replies
-
I was following the other thread of the discussion you both were having. I started noticing this issue after updating vue to 3.4.19. I tried following the stack trace like @SirH3nry did but took me on a wild goose chase of fairly basic usage of my stores. From what I can discern at glance it has to do with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
More information here: #10299
and here: f7ba97f
and here: https://vuejs.org/guide/essentials/computed.html#getters-should-be-side-effect-free
I'm not sure why I'm receiving this warning, after following the stack trace, it brought me to two locations that don't seem to be getters with side effects.
Here's the first occurrence:
and here's the second, the stack trace of the warning points to the watch, not the getter.
Beta Was this translation helpful? Give feedback.
All reactions