-
Notifications
You must be signed in to change notification settings - Fork 286
[Feature Request] Update to allow using new Rubocop auto-correct options #637
Comments
Locking rubocop to version |
This issue has not had activity for 30 days. It will be automatically closed in 7 days. |
This comment is to prevent auto-closing the issue. If maintainers want this closed we can close it, but I think this is a valid, ongoing request. |
This issue has not had activity for 30 days. It will be automatically closed in 7 days. |
Bump, these github actions are silly, 30 days... The maintainers haven't even commented on this yet. |
This issue has not had activity for 30 days. It will be automatically closed in 7 days. |
Commenting to keep this alive. Apologies for the email spam. |
Here's a pre-emptive bump with 4 days to go. |
@wingrunr21 what's with these github-actions? Can a label be added to this issue so that they don't need to be manually kept alive every 30 days? |
Cheers! |
For my opinion quick fix suggestion would be great for unsafe autocorrection. |
Robocop has recently (v0.87) updated their auto-correct system to provide two versions:
rubocop -A
(Auto-Correct) andrubocop -a
(Safe auto-correct)See: https://docs.rubocop.org/rubocop/0.88/usage/auto_correct.html
Currently this extension only runs safe-auto-correct, but it would be nice to provide the option to run the full "auto-correct" format via this extension.
Related Rubocop issue: rubocop/rubocop#8368
The text was updated successfully, but these errors were encountered: