Open buglavecz opened 2 months ago
workaround:
const myComputed = computed({
get() { return [{ item: 'a' }, { item: 'b' }].map(item => item); },
set() {}
});
this is unlikely to be related to this library and is probably a Vue core issue.
this is unlikely to be related to this library and is probably a Vue core issue.
@danielroe the strange thing is that the error only occurs in nuxt page components. so I thought it had something to do with this package...
oh, that does sound more like it's an issue with nuxt
however vue 2 is EOL (and so is Nuxt 2) so unfortunately I am not planning to take time to look further into this. (apologies!) I hope the workaround you provided will serve you well. đ
@danielroe okay, no problem. thanks your answer.
đ The bug I got this warning on just page component.
đ ī¸ To reproduce Steps to reproduce the behavior:
If define a computed property like this (array manipulate: map, find, filter etc):
If not return in the setup() function, then not show the warning message....
âšī¸ Additional context In the options API, that working fine.