-
-
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
Opting in to cops on a cop-by-cop basis? #986
Comments
Don't think that is possible at the moment (at least directly). @jonas054 might have more insight. I guess you can have a config that disabled all cops out-of-the box, inherit from it, and enable only the cops you want to enable.
Not sure what you mean. You can run a single cop with:
|
Sorry, I don't think I was clear: I was describing one use case that covered all three of those bullets, not three separate cases. You're right that That is, I want to run every Lint cop, and only some of the Style cops, and none of the other cops. It sounds like the best place to start is a config that explicitly disables every cop, but that would break as soon as any new cop is introduced, right? |
The way to achieve this is, as you suggest @fj, to copy But you're right that it would break when style cops are added in later versions. There's no way to disable by default and opt in. If we want to add such functionality, I think the best way would be to
|
👍 for running multiple cops with |
OK, I think that should be a comparatively straightforward task. I can work on a pull request, but I just want to point out that this would be a breaking change ( |
Yes, this is acceptable. We're pretty far away from a 1.0 release anyways. — On Thu, Apr 10, 2014 at 7:34 PM, John Feminella notifications@github.com
|
Part of solution for rubocop#986.
Part of solution for rubocop#986.
The documentation doesn't seem to cover the following use case:
.rubocop.yml
.Is something like that possible?
The text was updated successfully, but these errors were encountered: