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
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
The eslint linter has this feature to stop distracting, red error lines appearing everywhere while typing out things which is especially useful when fix-on-save is enabled. These "silenced" errors then appear on save if not already auto fixed.
Since the linter and the autofixer are seperate atom packages, it would not have the same immediate benefit for all users but it would a good option to include IMO.
The text was updated successfully, but these errors were encountered:
I would love to see an option that blocks lint until save, or debounce linting by 5 or 10 seconds after typing.
I can't imagine why the linter runs on every keystroke since it's basically guaranteed to fail.
This package is simply a provider of a service, you need to look into whatever consumer you have installed as to how often it gets called. For example if you are running linter you can either:
Uncheck "Lint on Change" to disable linting modified documents entirely (leaving only linting on save)
Change the "Lint on Change Interval" to a higher value (5 seconds = 5000 ms)
If stylelint is crashing on that input it's likely a bug in there that needs to be fixed, but without reliable steps to reproduce (which should be filed as a separate bug) it's impossible to say for sure.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
eslint
linter has this feature to stop distracting, red error lines appearing everywhere while typing out things which is especially useful when fix-on-save is enabled. These "silenced" errors then appear on save if not already auto fixed.Since the linter and the autofixer are seperate atom packages, it would not have the same immediate benefit for all users but it would a good option to include IMO.
The text was updated successfully, but these errors were encountered: