Edit me

detekt supports the Java (@SuppressWarnings) and Kotlin (@Suppress) style suppression. If both annotations are present, Kotlin’s annotation is favored!

To suppress an issue, the id of the issue must be written inside the values field of the annotation e.g. @Suppress("LongMethod", "LongParameterList", ...) The issue id is also exactly the id of the reporting rule.

If a LargeClass is reported, but that is totally fine for you codebase, then just annotate it:

@Suppress("LargeClass") // Yes, objects are also reported by the same rule.
object Constants {

Some rules like TooManyFunctions can be suppressed by using a file level annotation @file:Suppress("TooManyFunctions").