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
standard --fix does a lot of hard work for the user and should reduce instances of linter-rage when faced with sweeping changes, such as the new JSX single -> double quote rule: standard/eslint-config-standard#27.
However, standard --fix is new and many users will not know to even look for it. Some recent anecdotal evidence:
This new & handy feature could do with more promotion, especially when it's most applicable: when the user is staring at a wall of linter errors.
I'd submit a PR but it's not obvious what the wording should be or how this should be achieved.
Ideally the error message would span multiple lines like:
standard: Use JavaScript Standard Style (http://standardjs.com)
Try `standard --fix` to automatically fix problems.
But that's probably not possible in current setup as is. The tagline is printed in between standard: and the (homepage) in the following:
standard: Use JavaScript Standard Style (http://standardjs.com)
Without looking too deeply it looks like the formatting of the error message is applied by eslint. Perhaps there are other options to get it to print a different thing?
Embedding it on the one line as a part of the tagline looks like:
standard: Use JavaScript Standard Style. Try `standard --fix` to automatically fix problems. (http://standardjs.com)
This is maybe just acceptable in this form, though it is a bit wordy.
The tagline is not really the right place for this as it also infects --help (and perhaps other places?):
> standard --help
standard - Use JavaScript Standard Style. Try `standard --fix` to automatically fix problems. (http://standardjs.com)
Usage:
standard <flags> [FILES...]
If FILES is omitted, then all JavaScript source files (*.js, *.jsx) in the current
working directory are checked, recursively.
Certain paths (node_modules/, .git/, coverage/, *.min.js, bundle.js, vendor/) are
automatically ignored.
Flags:
…
Maybe this is ok though?
Overall: ¯\_(ツ)_/¯
The text was updated successfully, but these errors were encountered:
Problem
standard --fix
does a lot of hard work for the user and should reduce instances of linter-rage when faced with sweeping changes, such as the new JSX single -> double quote rule: standard/eslint-config-standard#27.However,
standard --fix
is new and many users will not know to even look for it. Some recent anecdotal evidence:This new & handy feature could do with more promotion, especially when it's most applicable: when the user is staring at a wall of linter errors.
Suggestion
Mention
--fix
whenever standard reports an error.Issue stemming from this comment: #564 (comment)
I'd submit a PR but it's not obvious what the wording should be or how this should be achieved.
Ideally the error message would span multiple lines like:
But that's probably not possible in current setup as is. The tagline is printed in between
standard:
and the(homepage)
in the following:Without looking too deeply it looks like the formatting of the error message is applied by eslint. Perhaps there are other options to get it to print a different thing?
Embedding it on the one line as a part of the tagline looks like:
This is maybe just acceptable in this form, though it is a bit wordy.
The tagline is not really the right place for this as it also infects
--help
(and perhaps other places?):Maybe this is ok though?
Overall:
¯\_(ツ)_/¯
The text was updated successfully, but these errors were encountered: