From 80a84945efd0a596324d9eb920d65774756a2cc3 Mon Sep 17 00:00:00 2001 From: Johnny Lim Date: Thu, 16 Jan 2025 00:49:04 +0900 Subject: [PATCH] Fix depth for NullAway subsections in reference docs Closes gh-34267 Signed-off-by: Johnny Lim --- framework-docs/modules/ROOT/pages/core/null-safety.adoc | 4 ++-- 1 file changed, 2 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 f36250025e8c..cb44685c1465 100644 --- a/framework-docs/modules/ROOT/pages/core/null-safety.adoc +++ b/framework-docs/modules/ROOT/pages/core/null-safety.adoc @@ -105,7 +105,7 @@ typical use cases. [[null-safety-guidelines-nullaway]] === NullAway -=== Configuration +==== Configuration The recommended configuration is: @@ -127,7 +127,7 @@ using JDK 22 or later (typically combined with the `--release` Java compiler fla expected baseline). It is recommended to enable the JSpecify mode only as a second step, after making sure the codebase generates no warning with the recommended configuration mentioned above. -=== Warnings suppression +==== Warnings suppression There are a few valid use cases where NullAway will wrongly detect nullness problems. In such case, it is recommended to suppress related warnings and to document the reason: