Skip to content

Feature suggestion: Ignore only given set of rules #15

@tomascapek

Description

@tomascapek

In my usage of this awesome tool I found out, that # bb: disable can sometimes hide other errors, which would be otherwise addressed. Let's consider following example:

deprecated_fn(42 + inner_fn())

So one day, first function became deprecated and thus rule DeprecatedFnCall was created. For some reason a programmer decided, that he still needs to keep that old deprecated function and so he disabled the warning.

deprecated_fn(42 + inner_fn()) # bb: disable

But the other day, inner_fn became deprecated too and I think you can see the problem now. If he'd been allowed to do something similar to what pylint does:

 deprecated_fn(42 + inner_fn()) # bb: disable = DeprecatedFnCall

With the creation of the new rule, he would be able to detect this fatal problem, because it would immediately show up as an error.

Of course, this is you project and this is only a suggestion :)

I am also willing to create this feature myself, if you like this idea and don't {want | have time} to deal with it.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions