Bug with files.associations config and SFC script tags

Similar to an older issue which was complaining about <template> tags in a SFC under a file association.

https://github.com/vuejs/vetur/issues/1480

Info

• Platform: Linux
• Vetur version: 0.31.3
• VS Code version: 1.52.0

Problem

    "files.associations": {
        "*.foo": "vue"
    },

<script>
</script>
<template>
</template>

Fails with: "Cannot find name 'script'"

Whereas the following succeeds:

<script lang="js">
</script>
<template>
</template>

[yoyo930021]

We don’t support files.associations. We have a lot of judgment based on file names. Vetur provide TypeScript/JavaScript feature with TypeScript language service. TypeScript language service don’t support custom filename extension.

If you want to support this option, you need a lot of energy. I don’t think we have enough development energy to do this.

[mryellow]

The more I understand how this handles extensions and custom blocks, the more I’m convinced this is a bug.

• *.foo will be scanned and <script lang="js"> will correctly be parsed.
• *.foo will be scanned and <script> will not be found. (Or rather it will be found but Vetur will complain about not knowing “script” blocks)

If it can find one. Why does it not find the other?