prospector icon indicating copy to clipboard operation
prospector copied to clipboard

Looking for a way to ignore specific rules at command line

Open aaronsteers opened this issue 5 years ago • 1 comments

Is your feature request related to a problem? Please describe.

Yes - this would have been an easy solution to #370 which is in regards to mutually exclusive rules enabled by default.

Describe the solution you'd like

I use prospector from visual studio code and I don't want to manage a profile file - it is not portable enough for my preferred use case. Instead, I want to be able to configure using command line args which I can add to my settings.json file in VS Code. Currently, there does not seem to be any way to ignore specific rules - except to either create a profile file or disable entire libraries.

FWIW, all other linters I've used so far have some kind of --ignore=rule-id or --disable=rule-id syntax which they accept via CLI execution.

Describe alternatives you've considered

The only solution I have right now is to either (1) manage a separate profile file (which I don't want to do), or (2) search for a suitable profile from the default list here and then pass it with --profile=profile-name. The problem with option 2 is that I will inevitably be turning off other rules that I might actually benefit from.

Additional context

For what it's worth, aside from the troubles I raised in #370, the rule I really want to turn off pylint(logging-format-interpolation) Frankly, I just don't believe in this PEP - for infinitesimally small chance at a performance boost, I write my string interpolation two different ways depending upon whether the compiler actually needs to run it or not? There are other ways to optimize for that, and this seems like a silly and outdated rule. 😄

aaronsteers avatar Mar 14 '20 21:03 aaronsteers

Any update on ability to do rule exclusions at command line?

aaronsteers avatar May 31 '20 15:05 aaronsteers