76
JetBrains
348 readers
2 users here now
A community for discussion and news relating to JetBrains and its products! https://www.jetbrains.com/
Related Communities
- !aqua@programming.dev
- !clion@programming.dev
- !datagrip@programming.dev
- !dataspell@programming.dev
- !fleet@programming.dev
- !goland@programming.dev
- !intellij@programming.dev
- !phpstorm@programming.dev
- !pycharm@programming.dev
- !rider@programming.dev
- !rubymine@programming.dev
- !rustrover@programming.dev
- !webstorm@programming.dev
Copyright © 2000-2024 JetBrains s.r.o. JetBrains and the JetBrains logo are registered trademarks of JetBrains s.r.o.
founded 2 years ago
MODERATORS
78
3
Make IntelliJ IDEA warn for potential NullPointerExceptions during unboxing without assuming everything is @Nullable?
(stackoverflow.com)
Link to a (frustratingly) deleted question on Stack Overflow. Text and image copied below incase you don't have the ability to see it. (Not sure why the image shows multiple times.)
Is there any way to more granularly control IntelliJ IDEA's inspections' "Nullability and data flow problems" option "Treat non-annotated members and parameters as @Nullable"? Preferably for unboxing specifically?
I am aware I can use a variety of @Nullable annotations in a variety of places in the code to make the warnings appear. That's not always an option as the place the boxed primitives are coming from may be other libraries you don't have control over. (Imagine if the Holder record below was from a different project.) I included other examples below to illustrate my point.
public class Sample {
private final Boolean value;
public Sample(Boolean value) {
this.value = value;
}
private boolean isValue() {
return value; // I would like a warning here
}
private static Boolean boxedTrue() {
return true;
}
private static boolean unboxedTrue() {
return boxedTrue(); // No warning here, but that's understandable since never null
}
private static Boolean boxedNull() {
return null;
}
private static boolean unboxedNull() {
return boxedNull(); // Only warning in the file (by default)
// "Unboxing of 'boxedNull()' may produce 'NullPointerException'
}
public record Holder(Boolean value) {}
public boolean openHolder(Holder holder) {
return holder.value(); // I would like a warning here
}
}
When "Treat non-annotated members and parameters as @Nullable" is enabled, the following gives warnings. While that makes sense given the name of the option, there is code like this literally everywhere. It adds hundreds of warnings to my project. I'm trying to find more granular choices.
public static ZonedDateTime timeStuff(LocalDateTime localDateTime, ZoneId zoneId) {
return localDateTime.atZone(zoneId); // I do not want warnings for this
}
I see that the Java Class Library has JetBrains annotations despite not actually being annotated. Is there perhaps some way to add these automatically to libraries if there is no better way to control the inspection?
79
80
81
1
Well, I’m pleased with #Zed, but you ain’t programming “at the speed of thought” yet.
(files.mastodon.social)
82
83
84
85
1
It's interesting that Jetbrain's CLion Nova is otherwise an excellent IDE, but it can be just glacially slow at times. For instance when bringing up the "fix stuff" popup for a simple "replace with
(static.toot.community)
It's interesting that Jetbrain's CLion Nova is otherwise an excellent IDE, but it can be just glacially slow at times. For instance when bringing up the "fix stuff" popup for a simple "replace with auto" hover suggestion, it can take up to 10 seconds for the popup to show. Clearly the internal structures are broken and/or totally unoptimised. Cmd-clicking on a method can also lead to "Resolving references" for some seconds.
/cc @jetbrains
86
87
88
89
90
91
92
93
7
Create Custom Code Inspections in IntelliJ IDEA – and More – With Qodana 2024.1
(blog.jetbrains.com)
94
95
96
97
98
99
100