-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Suggestion to check that all ignores specified in the configuration are used to ignore something and report any that are not.1 If an ignore is ineffective it should probably cause dirty-waters to fail hard (i.e. non-zero exit code) and it may need to be an opt-in feature (or else have an opt-out available).
The reason I believe this is useful is that once something you ignored has been resolved you probably do not want to just accept that smell again in the future. If you do not know that an ignore is no longer effective you won't realize the smell has been resolved (which is probably nice to know about in any case), and you might inadvertently introduce it again at a later point in time.
Footnotes
-
This is similar to the
--report-unusedoption I created for a related project. ↩