From d83be7c33a9d7926409ccecdaf499708dc35842e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Deleuze?= Date: Tue, 21 Jan 2025 15:23:46 +0100 Subject: [PATCH] Mention the Nullness API in the null safety refdoc See gh-34261 --- framework-docs/modules/ROOT/pages/core/null-safety.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/framework-docs/modules/ROOT/pages/core/null-safety.adoc b/framework-docs/modules/ROOT/pages/core/null-safety.adoc index cb44685c14..914e7eadb9 100644 --- a/framework-docs/modules/ROOT/pages/core/null-safety.adoc +++ b/framework-docs/modules/ROOT/pages/core/null-safety.adoc @@ -12,8 +12,9 @@ both Java by leveraging some tooling (https://github.com/uber/NullAway[NullAway] annotations such as IntelliJ IDEA or Eclipse) and Kotlin where JSpecify annotations are automatically translated to {kotlin-docs}/null-safety.html[Kotlin's null safety]. -`@Nullable` annotations are also used at runtime to infer if a parameter is optional or not, for example via -{spring-framework-api}/core/MethodParameter.html#isOptional()[`MethodParameter#isOptional`]. +The {spring-framework-api}/core/Nullness.html[`Nullness` Spring API] can be used at runtime to detect the nullness of a +type usage, a field, a method return type or a parameter. It provides full support for JSpecify annotations and +Kotlin null safety, as well as a pragmatic check on any `@Nullable` annotation (regardless of the package). [[null-safety-libraries]] == Annotating libraries with JSpecify annotations