Update to NullAway 0.12.15 and fix new warnings #36054
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
FYI @sdeleuze |
spring-projects-issues
added
the
status: waiting-for-triage
Signed-off-by: Manu Sridharan <[email protected]>
msridhar
force-pushed
the
nullaway-0.12.15-fixes
branch
from
1ac5243 to
b39f321
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new warnings are a consequence of uber/NullAway#1371, which better detections annotations on type arguments in return types. Fortunately, the fixes are straightforward. Note that writing
@Nullable Voidis required by JSpecify (see jspecify/jspecify#51). This is not yet checked exhaustively by NullAway, but some instances were caught here.