Add @Nullable annotation where applicable
#66
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
modmuss50
approved these changes
Oct 16, 2023
NebelNidas
added a commit
to NebelNidas/mapping-io
that referenced
this pull request
Nov 7, 2023
* Annotate all nullable parameters with `@Nullable` Also fix some inconsistent names * Annotate all nullable method return types with `@Nullable` * Annotate all nullable public fields with `@Nullable`
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.
Clearly defines where consumers must be careful about potential null values and where only non-null values are allowed. Unannotated elements have to be considered null-hostile by default.