Kael
Kael
This isn't a bug, you have to do the pagination on your backend.
It seems to be intentional, I guess so you can't accidentally access computed properties via a method? https://github.com/vuejs/vue/blob/3b43c81216c2e29bd519c447e930d6512b5782e8/types/options.d.ts#L34 edit: https://github.com/vuejs/vue/pull/6391/commits/540a38fb21adb7a7bc394c65e23e6cffb36cd867, https://github.com/vuejs/vue/pull/5887#discussion_r122128852
They don't exist yet: https://codepen.io/kaelwd/pen/pOErZw?editors=0011
Yeah I know, it is a bit silly. Just a guess as to why they might've done that.
Typescript 3.9 has made this even worse, I have to specify return types for methods too now.
Pretty sure this is intentional, otherwise you wouldn't be able to assign a number to it. ```ts this.myComputedProp = 1 // Type '1' is not assignable to type 'string' ```
If the types could be different then `this.myComputedProp = this.myComputedProp` would be an error.
This is still blocked by https://github.com/vuejs/core/pull/6095
If you're wrapping the whole page in `` you might as well just disable ssr entirely.
Hmm I guess this would've been fixed by #16546 As of 952e36d35bc7af6ef30d0b2b8c08c1ab7838c637 it does at least work if the objects have all the same keys