You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While typing most of the times file has invalid syntax until developer finishes typing or editing. Running linting on invalid file shows errors, which doesn't help, because editing process is not finished by developer.
eslint.run - run the linter onSave or onType, default is onType.
I would like to see similar option for this extension.
How does this feature solve the problem?
When linting is configured to run only onSave, then developer would see less useless errors about invalid syntax. Because usually, when we save file it has valid syntax.
What are some alternatives to this feature?
I see no other alternatives.
Code of Conduct
I agree to follow vscode-stylelint's Code of Conduct
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
While typing most of the times file has invalid syntax until developer finishes typing or editing. Running linting on invalid file shows errors, which doesn't help, because editing process is not finished by developer.
ESLint extension has this option:
eslint.run
- run the linteronSave
oronType
, default isonType
.I would like to see similar option for this extension.
How does this feature solve the problem?
When linting is configured to run only
onSave
, then developer would see less useless errors about invalid syntax. Because usually, when we save file it has valid syntax.What are some alternatives to this feature?
I see no other alternatives.
Code of Conduct
The text was updated successfully, but these errors were encountered: