Flo Edelmann

@Yhspehy I see you are [using](https://github.com/Yhspehy/vue3.3-import-type-bug/blob/eebb2cd8f21fa6d2818348bd6362504010e297e8/package.json#L26) `eslint-plugin-vue` v9.11.0. In [v9.13.0](https://github.com/vuejs/eslint-plugin-vue/releases/tag/v9.13.0), support for imported types was added. Please try upgrading to the latest version and see if the bug remains. If...

Could you please update the version in the production repo?

Related: https://github.com/vuejs/eslint-plugin-vue/issues/2142 and https://typescript-eslint.io/rules/switch-exhaustiveness-check

`company-i-d` indeed looks wrong, but why not name the prop `companyId`, so it is kebab-cased to `company-id`? I think an `ignore` option could be added, but it would be very...

See also https://typescript-eslint.io/rules/switch-exhaustiveness-check

A pull request to improve the detection is welcome

Are you using Vue 2 or Vue 3? TypeScript syntax in template expressions is not allowed in Vue 2: https://v2.vuejs.org/v2/guide/migration-vue-2-7.html#Behavior-Differences-from-Vue-3

It should work in Vue 3. But since there is no response, I'm closing this. Feel free to comment new information or open a new issue.

I see that we indeed don't have a test case in https://github.com/vuejs/eslint-plugin-vue/blob/v9.17.0/tests/lib/rules/no-parsing-error.js to explicitly test TypeScript syntax in Vue 3, so maybe we don't support it. A pull request to...

`"vue/component-api-style": ["error", ["script-setup"]]` should still work; that rule was not changed in the last version. Could you please link to a repository where the issue can be reproduced?