You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every task instance creates a bunch of computed which can be costly, especially in Vue 2. Task instances are also created often asynchronously - after user interaction or when other async logic finishes and os on. That makes these new computeds not part of the component lifecycle.
Fixing this would require a major overhaul. It would be nice if it would be possible to somehow pass the vm from task to the taskinstance and then to the computed. That would probably fix the issues in Vue 2.
Every task instance creates a bunch of
computed
which can be costly, especially in Vue 2. Task instances are also created often asynchronously - after user interaction or when other async logic finishes and os on. That makes these new computeds not part of the component lifecycle.Fixing this would require a major overhaul. It would be nice if it would be possible to somehow pass the
vm
from task to the taskinstance and then to thecomputed
. That would probably fix the issues in Vue 2.https://antfu.me/posts/async-with-composition-api#explicitly-bound-the-instance - perhaps this trick could be done with computed too?
The text was updated successfully, but these errors were encountered: