Skip to content
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

[Feature]: Configure when linting runs #445

Open
1 task done
hudochenkov opened this issue Feb 20, 2023 · 1 comment
Open
1 task done

[Feature]: Configure when linting runs #445

hudochenkov opened this issue Feb 20, 2023 · 1 comment
Labels
type: enhancement a new feature that isn't related to rules

Comments

@hudochenkov
Copy link
Member

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 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
@pikeas
Copy link

pikeas commented Aug 30, 2024

+1, files will typically fail multiple lint rules while being worked on. For example, block-no-empty:

.new-class {

}

This displays three lines with bright red error (or warning) squiggles, which is extremely visually distracting while working.

It would be great if Stylelint provided an option to run only on save instead of while typing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement a new feature that isn't related to rules
Projects
None yet
Development

No branches or pull requests

2 participants