From 87d0f20e014bc643f15f098aed72ac7a61a1aa21 Mon Sep 17 00:00:00 2001 From: cpovirk Date: Fri, 5 May 2023 15:09:51 -0700 Subject: [PATCH] Recognize more JSpecify annotations as type-use: - the `@Nullable` from the new package - `@NonNull` from both packages, even though it appeared in the old package only very briefly Note that there's no case in which it would make sense to use our existing refactorings to insert `@NonNull`. But that may change, and I figured I might as well address it while I was here. PiperOrigin-RevId: 529824478 --- .../google/errorprone/bugpatterns/nullness/NullnessUtils.java | 3 +++ 1 file changed, 3 insertions(+) diff --git a/core/src/main/java/com/google/errorprone/bugpatterns/nullness/NullnessUtils.java b/core/src/main/java/com/google/errorprone/bugpatterns/nullness/NullnessUtils.java index 180b50e1d87..03cd4154604 100644 --- a/core/src/main/java/com/google/errorprone/bugpatterns/nullness/NullnessUtils.java +++ b/core/src/main/java/com/google/errorprone/bugpatterns/nullness/NullnessUtils.java @@ -375,6 +375,9 @@ private static boolean isTypeUse(String className) { case "libcore.util.Nullable": case "org.checkerframework.checker.nullness.compatqual.NullableType": case "org.checkerframework.checker.nullness.qual.Nullable": + case "org.jspecify.annotations.NonNull": + case "org.jspecify.annotations.Nullable": + case "org.jspecify.nullness.NonNull": case "org.jspecify.nullness.Nullable": return true; default: