docs(gradle): Hint to users as to how to see the unused rules with the current gradle implementation #7328
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Currently due to the way the Gradle plugin is written when
failBuildOnUnusedSuppressionRule
(and some other analyzers) are used you just getAnalysis Failed
which is not much fun.Short of improving the way exceptions are logged with the plugin, or better integrating logging with Gradle lifecycle - this at least tells folks how to see the unused rules, e.g
Have test cases been added to cover the new functionality?
N/A