MDS/openide
1
0
Fork 0
mirror of https://gitflic.ru/project/openide/openide.git synced 2026-09-27 10:03:11 +07:00
Code Issues Packages Projects Releases Wiki Activity

[java] JSpecifyConformanceAnnotationTest: update comment about catch parameter nullness

Browse Source 
Related to IDEA-377763 Intrinsically NonNull exception parameter cannot be assigned null

GitOrigin-RevId: 94b3ae8452deca39d6162d926e2a457e4275212a
This commit is contained in:
Tagir Valeev
2025-10-01 15:50:23 +00:00
committed by intellij-monorepo-bot
parent 960e3448ae
commit 216eddbbf8
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
java/java-tests/testSrc/com/intellij/java/codeInspection/JSpecifyConformanceAnnotationTest.java
+5 -2
View File
@@ -92,8 +92,11 @@ public class JSpecifyConformanceAnnotationTest extends LightJavaCodeInsightFixtu
private static boolean suppressWarning(@NotNull String message, String fileName, Integer offset) {
Set<Pair<String, Integer>> suppressed = Set.of(
Pair.create("Other.java", 72), // see: IDEA-377763
Pair.create("Other.java", 70) // see: IDEA-377763
// These two exceptions are expected: unlike JSpecify, we don't assign NotNull nullness to non-final catch parameter
// Instead, we are doing the flow analysis and may change the nullness during the variable lifetime
// See IDEA-377763 for details
Pair.create("Other.java", 72),
Pair.create("Other.java", 70)
);
LineColumn column = StringUtil.offsetToLineColumn(message, offset);
return suppressed.contains(Pair.create(fileName, column.line));