IntentionallyNonStaticCompanionApi
Acknowledges that the annotated companion object member - or every member inside the annotated companion object or class - is deliberately reachable from Java only through the companion instance.
The library-api-watchdog compiler plugin warns, in JVM compilations, about publicly visible companion object functions without @JvmStatic and constant-shaped companion vals without @JvmField: both compile to members of the nested Companion class, so Java callers have to go through Outer.Companion. Prefer exposing such members on the outer class itself (@JvmStatic, @JvmField, const val) or hiding them from Java (@JvmSynthetic), and apply this annotation to suppress the warnings when the companion-instance access path is intended. On a class - the companion object itself or its outer class - it covers every member inside.
See the check documentation for rationale and examples: companion functions, companion constants.
Parameters
why the companion-instance access path is intended.
free-form explanation of the exemption. May be empty only when reason explains the exemption on its own (ExemptionReason.FOR_BACKWARDS_COMPATIBILITY, ExemptionReason.API_DESIGN).