chore: use jspecify nullable annotations #241
Merged
Conversation
This file contains 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
PhilippHeuer
changed the title
PhilippHeuer
force-pushed
the
chore/jspecify
branch
from
b10694f to
c07341c
Compare
iProdigy
reviewed
Feb 6, 2025
PhilippHeuer
force-pushed
the
chore/jspecify
branch
from
c07341c to
e845204
Compare
iProdigy
reviewed
Feb 6, 2025
core/src/main/java/com/github/philippheuer/events4j/core/EventManager.java
Show resolved
Hide resolved
…Manager.java Co-authored-by: iProdigy <[email protected]>
iProdigy
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Additional Information
As events4j does not have nullable annotations yet, this is prob. a good first project to adopt jspecify in.
IntelliJ should already support jspecify -> https://jspecify.dev/docs/whether/#nullness-checker-support-for-jspecify