-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong: Missing semicolon (semicolon) warning #15
Comments
I noticed the same thing when I just spun up a template project with vue-cli 3.0. Which I guess is just a requirement (as listed on the quickstart.) |
I'm experiencing this too, and it's driving me mad. I think I need to remove the extension. |
I noticed the same thing too. If I disable the extension, I can't find another one to lint Vue SFC. |
Fixed it. Turns out I had some bad code. Make sure that:
|
@Nfinished Right. There's nothing wrong with this file, obviously, but it's other files affecting this one. (see my post above yours) |
𝓬𝓻𝓲𝓹𝓮𝓼 |
I know, tell me about it. I spent hours trying to figure out what was wrong. I still don't understand why having some components use JS and some use TS is a problem. But it was causing issues in VS Code, as Prettier wouldn't work either. |
I will say this, though: it's not possible to have a .vue file without a @prograhammer Is this something you could address? |
Woops. Actually, all this code was needed: <script lang="ts">
import Vue from 'vue';
export default Vue.extend();
</script> Otherwise, |
I use this extension together with It works fine most of the time, but as soon as you have a component with self-closing Before:
After:
After it becomes very annoying I temporarily disable auto-fixing, or execute VSCode's save without formatting. |
When a .vue template is missing the <script type=ts></script> the ts-line-vue has false positive warnings
expected behavior is no warnings in that case, like here
The text was updated successfully, but these errors were encountered: