Is --check and --except actually contradictory to the point of this project?
jhauberg opened this issue · 2 comments
As I see it, the entire point of comply is to provide a single ubiquitous style for any project; that means it shouldn't be configurable. Being able to exclude or include certain rules contradicts that.
I definitely use these options occasionally, but really only when debugging or trying out a new rule.
Should these options just be developer flags instead? That means we need a separate usage docstring depending on the situation? I don't like that a lot...
Alternatively, we could emit a diagnostic about the use of these flags saying something like it not being recommended?
I suppose --only-severe also goes here...
These options have their uses. They're now listed as non-compliant, to indicate that they shouldn't typically be used.