-
Notifications
You must be signed in to change notification settings - Fork 213
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
Improve support for reporting cop errors to rubocop. #452
Labels
enhancement ✨
New feature or request
Comments
rubocop issue template at present: https://github.com/rubocop/rubocop/blob/3360eac8244c1f2dce49cfffa00b6f3611c2de6b/.github/ISSUE_TEMPLATE/bug_report.md |
💯 this makes perfect sense and would make life easier for our Rubocop-maintaining friends |
patrickbrown-dev
added a commit
to patrickbrown-dev/standard
that referenced
this issue
Sep 28, 2022
This addresses the second feature mentioned in standardrb#452. For context, when debugging a RuboCop issue a user is asked to supply the output of `rubocop -V`, and this streamlines this process for standard users.
patrickbrown-dev
added a commit
to patrickbrown-dev/standard
that referenced
this issue
Sep 28, 2022
This addresses the second feature mentioned in standardrb#452. For context, when debugging a RuboCop issue a user is asked to supply the output of `rubocop -V`, and this streamlines this process for standard users.
patrickbrown-dev
added a commit
to patrickbrown-dev/standard
that referenced
this issue
Sep 28, 2022
This addresses the second feature mentioned in standardrb#452. For context, when debugging a RuboCop issue a user is asked to supply the output of `rubocop -V`, and this streamlines this process for standard users.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When encountering bugs with rubocop cops, one would attempt to open Issues against rubocop.
Rubocop requests that issues include the output with:
rubocop --debug
to include additional debug information;and
rubocop -V
to include full version information.It appears that
standardrb --debug
does not generate any additional debug information. Whether it actually passes the flag along to rubocop is unclear. But the output of a scan is identical both with and without the flag.-V does not emit version information at all. It triggers a regular scan. (So evidently,
-V
isn't even recognized as a valid option.) Ideally,-V
would emit all the same information asrubocop -V
, plus standardrb's own version. Ideally, it would be in the same format as rubocop's so one couldstandard -V | pbcopy
and have the output paste-able into a rubocop issue.Between these two items, I think #2 is arguable more important and valuable.
The text was updated successfully, but these errors were encountered: