When using defineComponent in Vue 2, unknown properties are infered to "any"

[victorgarciaesgi]

• I have searched through existing issues
• I have read through docs
• I have read FAQ
• I have tried restarting VS Code or running Vetur: Restart VLS

Info

• Platform:macOS
• Vetur version: 0.30.3
• VS Code version: 1.51.1

Problem

When using defineComponent from @vue/composition-api, unknown properties do not throw errors in template.

import { defineComponent } from '@nuxtjs/composition-api';

export default defineComponent({
     name: 'Test',
     setup(_, {root}) {
     // .....
     }
})

[yoyo930021]

if you set "vetur.validation.interpolation": true?

The unknown properties are infered to "any".
This thing is correct.

[victorgarciaesgi]

@yoyo930021 I had it activated already.

All my projet is written class-component style using (vue/nuxt)-property-decorators, and when I'm using a class, Vetur throws an error for unknown properties.
So I thought using defineComponent would have the same behaviour.

import { Component, Vue } from 'nuxt-property-decorator';

@Component({
// ...
})
export default class SocietyUuid extends Vue {
// ...
}

Current Vetur settings

{
  "vetur.validation.template": true,
  "vetur.validation.script": true,
  "vetur.format.defaultFormatter.html": "prettier",
  "vetur.validation.interpolation": true,
  "vetur.experimental.templateInterpolationService": true,
  "vetur.completion.autoImport": true,
  "vetur.completion.tagCasing": "initial",
  "vetur.validation.templateProps": true,
  "vetur.grammar.customBlocks": {
    "page-query": "graphql",
    "static-query": "graphql"
  },
}

[yoyo930021]

It's a problem in @vue/compostion-api.

[yoyo930021]

Fixed in @vue/composition-api in new release

[victorgarciaesgi]

Thanks for the fast fix @yoyo930021! Massive respect for your work on Vetur!