From 2af0b42ad958f479fbedd4ba6f77f43104828ece Mon Sep 17 00:00:00 2001
From: Havoc Pennington <hp@pobox.com>
Date: Sun, 29 Mar 2015 10:31:51 -0400
Subject: [PATCH] Mention getIsNull and hasPathOrNull as exceptions to "Config
 hides null" docs

---
 config/src/main/java/com/typesafe/config/Config.java | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/config/src/main/java/com/typesafe/config/Config.java b/config/src/main/java/com/typesafe/config/Config.java
index a8395c15..68031861 100644
--- a/config/src/main/java/com/typesafe/config/Config.java
+++ b/config/src/main/java/com/typesafe/config/Config.java
@@ -75,8 +75,9 @@ import java.util.concurrent.TimeUnit;
  * conceptually, {@code ConfigValue}s with a {@link ConfigValue#valueType()
  * valueType()} of {@link ConfigValueType#NULL NULL} exist in a
  * {@code ConfigObject}, while a {@code Config} treats null values as if they
- * were missing.
- * 
+ * were missing. (With the exception of two methods: {@link Config#hasPathOrNull}
+ * and {@link Config#getIsNull} let you detect <code>null</code> values.)
+ *
  * <p>
  * <strong>Getting configuration values</strong>
  *