Feature Request: fail when a rule at level "warn" doesn't trigger.
Open
- Dominant language
- Java
- Stars
- 7.2k
- Forks
- 820
- Avg merge
- 5h 9m
- Merged PRs (30d)
- 50
Description
In a large installation with sub-projects, sometimes some projects break different rules than others. If the goal is to eliminate all known issues in a codebase, some sub-projects may set a rule to `warn` while the issues are worked out.
```
allProjects:
error("ReturnsNullCollection")
legacyProject:
warn("ReturnsNullCollection")
```
It would be nice for maintainers to be able to validate that all rules specified at `warn` are actually still needed at that level.
```
legacyProject:
// must be removed when last instance of this rule is fixed in legacyProject.
mustWarn("ReturnsNullCollection")
```
Contributor guide
Assessment
This issue has not been assessed yet.