[Validator] Mention IsNull in Basic Constraints

Author: wkania

reference/constraints/IsFalse.rst

@@ -107,6 +107,8 @@ method returns **false**:
             // ...
         }
 
+.. include:: /reference/constraints/_null-values-are-valid.rst.inc
+
 Options
 -------
 

reference/constraints/IsTrue.rst

@@ -111,6 +111,8 @@ Then you can validate this method with ``IsTrue`` as follows:
 
 If the ``isTokenValid()`` returns false, the validation will fail.
 
+.. include:: /reference/constraints/_null-values-are-valid.rst.inc
+
 Options
 -------
 

reference/constraints/Type.rst

@@ -148,6 +148,8 @@ This will check if ``emailAddress`` is an instance of ``Symfony\Component\Mime\A
     The feature to define multiple types in the ``type`` option was introduced
     in Symfony 4.4.
 
+.. include:: /reference/constraints/_null-values-are-valid.rst.inc
+
 Options
 -------
 

reference/constraints/_null-values-are-valid.rst.inc

@@ -0,0 +1,6 @@
+.. note::
+
+    As with most of the other constraints, ``null`` is
+    considered a valid value. This is to allow the use of optional values.
+    If the value is mandatory, a common solution is to combine this constraint
+    with :doc:`NotNull </reference/constraints/NotNull>`.