-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add Exclude items to the DisabledConfigFormatter output #1980
Conversation
👍 👌 👏 |
I think this. I think something similar was proposed in the past. I'm just worried about cases where there may be hundreds of files in the exclude list, but there's no denying you get a better overview of what remains to be fixed in your code. @jonas054 What do you think? |
I could always add a threshold for the maximum amount of items to display, with a fallback to |
More 👍 👏 |
Sounds reasonable. |
I chose a limit of 15, for no reason; other than I think 10 is too low, and 20 is too high. Any thoughts? |
Add a changelog entry and we're good to merge. |
99a7da2
to
4a32140
Compare
Done, Glad I could help :) |
Can you just squash all 3 commits into one? |
4a32140
to
8cf529b
Compare
@bbatsov Done and done! |
Add Exclude items to the DisabledConfigFormatter output
Thanks! |
This is the best... thanks all! |
I was testing some legacy code by using
--auto-gen-config
, and found it frustrating that trivial Cops had been disabled due to trival issues in one or two files.I didn't want to disable Whitespace Formatting, or other Style rules in any new code; so I thought I'd play around with the generator to Exclude relative file paths.
An example of what I managed to make it output, is as follows:
This way, its easier to globally disable Cops in my
.rubocop.yml
, and have a checklist of files to fix in my.rubocop_todos.yml
, instead of globally disabling rules the rest of my code abides by.What do you think?