Array get error type in v-for

[yoyo930021]

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: macOS
• Vetur version: 0.24.0 (master)
• VS Code version: 1.43.0

Problem

Wrong: readonly never[]
Correct: readonly { id: number; text: string; list: never[]; }[]

PS. show virtual file is correct.

Reproducible Case

https://github.com/yoyo930021/vetur-int-bug/blob/master/src/components/HelloWorld.vue

[ktsn]

Hmm, that's weird. If I copy and paste the virtual code into the script block, it infers correct type.

[yoyo930021]

Really weird.

I also check about virtual code in project.
https://github.com/yoyo930021/vetur-int-bug/blob/master/src/components/Test.vue

[ktsn]

If it is with explicit interface annotation, the type will be correct:

import { defineComponent, computed } from '@vue/composition-api'

interface Group {
  id: number
  text: string
  list: string[]
}

export default defineComponent({
  setup() {
    const groups = computed<Group[]>(() => {
      const result = []
      result.push({
        id: 1,
        text: '',
        list: []
      })
      return result
    })
    return {
      groups
    }
  }
})

[yoyo930021]

This is also correct.

import { defineComponent, computed } from "@vue/composition-api";

export default defineComponent({
  setup() {
    const groups = computed(() => {
      const result: { id: number, text: string, list: string[]}[] = []
      result.push({
        id: 1,
        text: '',
        list: []
      })

      return result;
    });

    return {
      groups
    };
  }
});

I think problem when typescript automatically infer types.

[yoyo930021]

I found the problem.

vetur/server/src/services/typescriptService/serviceHost.ts

Line 401 in dcf66c4

noImplicitAny: false,

When noImplicitAny: true or remove this line, array will get correct type.

I think we can remove this line for respect user settings.

[ktsn]

Hmm, I see. I set noImplictAny for template service because user can write a function in template. e.g.:

<template>
  <button @click="(event) => onClick(event)">Click</button>
</template>

I guess we could just remove this option and filter implicit any errors out if it comes from template region.