-
Notifications
You must be signed in to change notification settings - Fork 286
Only lint on save #308
Comments
Good idea, though personally I think this is beyond the scope of our extension. Even much more advanced linters (like vscode eslint) don't support this option. If our linter worked great you probably wouldn't want this feature anyway :) |
This can be supported similar to how TSLint supports it (see microsoft/vscode-tslint#68). Adding to v1 milestone |
VSCode ESLint does actually support this option, with |
Whoops. This public shaming is working - maybe I'll submit a PR. :) I've been meaning to dig into this more to examine other issues like #238, #262 and #307. Only if you aren't working on it, @wingrunr21. I see you assigned this to yourself... |
If you want to PR against the current codebase go ahead. I'm planning on mirroring the eslint/tslint support on the language server side. |
Is this still an issue using 0.20.0? |
This issue has not had activity for 30 days. It will be automatically closed in 7 days. |
Is it possible to make it so that this extension only lints on save, so that we don't errors while still writing code? Like the warning for unused variables?
The text was updated successfully, but these errors were encountered: