Support any nullable annotation for mark argument or field as nullable #3666
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
Signed-off-by: Valeriy Vyrva <[email protected]>
|
Site with contributor license agreement, mentioned in the PR template, is down at this moment. |
|
The link in the PR template, unfortunately, has been down for quite some time. Related PR : #3228 |
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.
Prior to this change, only the Spring Framework annotation
@org.springframework.lang.Nullablecould be used to denote nullable method arguments or class fields.However, numerous equivalent annotations exist, and different projects may utilize alternatives from different sources.
This change extends support to any annotation with equivalent semantics, allowing it to mark arguments or fields as nullable.