From a78ff470d7019a3cbf550ed3a7412340e18992e7 Mon Sep 17 00:00:00 2001
From: Yonel Ceruto <yonel.ceruto@scnd.com>
Date: Sun, 22 Sep 2024 11:34:16 -0400
Subject: [PATCH] documenting non-empty parameters

---
 configuration.rst | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/configuration.rst b/configuration.rst
index 36dceae1b71..52dc9b98c95 100644
--- a/configuration.rst
+++ b/configuration.rst
@@ -382,6 +382,25 @@ a new ``locale`` parameter is added to the ``config/services.yaml`` file).
     They are useful when working with :ref:`Compiler Passes </service_container/compiler_passes>`
     to declare some temporary parameters that won't be available later in the application.
 
+Configuration parameters are usually validation-free, but you can ensure that
+essential parameters for your application's functionality are not empty::
+
+    // ContainerBuilder
+    $container->parameterCannotBeEmpty('app.private_key', 'Did you forget to configure a non-empty value for "app.private_key" parameter?');
+
+If a non-empty parameter is ``null``, an empty string ``''``, or an empty array ``[]``,
+Symfony will throw an exception with the custom error message when attempting to
+retrieve the value of this parameter.
+
+.. versionadded:: 7.2
+
+    Validating non-empty parameters was introduced in Symfony 7.2.
+
+.. note::
+
+    Please note that this validation will *only* occur if a non-empty parameter value
+    is retrieved; otherwise, no exception will be thrown.
+
 .. seealso::
 
     Later in this article you can read how to