Suppressing lint issues in pure Java/Kotlin projects

[Zac Sweers]

Since `@SuppressLint` is not available in these projects, are comments the only way to suppress in these? Would you consider adding an annotations artifact (or adding to `androidx.annotation`) to cover these? Or consider supporting `@SuppressWarnings`/`@Suppress` in Java/Kotlin like Error-Prone and Detekt do?

[Tor Norbye]

@Suppress and @SuppressWarnings should already be working (and have been for years) -- if they do not please file a bug with repro instructions!

-- Tor

P.S. https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:lint/libs/lint-api/src/main/java/com/android/tools/lint/client/api/LintDriver.kt;l=3902;drc=b96013d3af9f61f3cd3fba1e3d1bc228cbccc943

On Wed, Sep 1, 2021 at 8:43 PM Zac Sweers <zac.s...@gmail.com> wrote:

Since `@SuppressLint` is not available in these projects, are comments the only way to suppress in these? Would you consider adding an annotations artifact (or adding to `androidx.annotation`) to cover these? Or consider supporting `@SuppressWarnings`/`@Suppress` in Java/Kotlin like Error-Prone and Detekt do?

--
You received this message because you are subscribed to the Google Groups "lint-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lint-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lint-dev/596255b3-e97c-4dd9-a665-dcb2d8d9cb7fn%40googlegroups.com.

[Zac Sweers]

Interesting, in testing it looks like the issue I'm stuck on is a custom lint we have to ensure `@Target` annotations include FIELD. The case I'm trying to suppress looks like this.

```
@Target(AnnotationTarget.FUNCTION)
@Retention(AnnotationRetention.RUNTIME)
@JsonQualifier // For access in Moshi deserialization
annotation class SlackEndpoint(...)
```

Where our lint requires that `@Target` includes `FIELD`. Using `@Suppress("MoshiUsageQualifierTarget")` on the class or file doesn't appear to work though. `//noinspection MoshiUsageQualifierTarget` however does work. Want me to file an issue?