[Configuration] Add documentation about ignore_not_found option.

Author: pulzarraider

configuration/configuration_organization.rst

@@ -141,7 +141,7 @@ when importing it from any other configuration file:
 
         # config/services.yaml
         imports:
-            - { resource: '/etc/sites/mysite.com/parameters.yaml', ignore_errors: true }
+            - { resource: '/etc/sites/mysite.com/parameters.yaml', ignore_not_found: true }
 
         # ...
 
@@ -157,7 +157,7 @@ when importing it from any other configuration file:
                 https://symfony.com/schema/dic/symfony/symfony-1.0.xsd">
 
             <imports>
-                <import resource="/etc/sites/mysite.com/parameters.yaml" ignore-errors="true"/>
+                <import resource="/etc/sites/mysite.com/parameters.yaml" ignore-not-found="true"/>
             </imports>
 
             <!-- ... -->
@@ -166,17 +166,63 @@ when importing it from any other configuration file:
     .. code-block:: php
 
         // config/services.php
-        $loader->import('/etc/sites/mysite.com/parameters.yaml', null, true);
+        use Symfony\Component\Config\Loader\FileLoader;
+
+        $loader->import('/etc/sites/mysite.com/parameters.yaml', null, FileLoader::IGNORE_FILE_NOT_FOUND);
 
         // ...
 
+.. versionadded:: 4.4
+
+    The ``ignore_not_found`` option was introduced in Symfony 4.4.
+
 .. tip::
 
-    The ``ignore_errors`` option (which is the third optional argument in the
+    The ``ignore_not_found`` option (which is the third optional argument in the
     loader's ``import()`` method) silently discards errors when the loaded file
     doesn't exist. This is needed in this case because most of the time, local
     developers won't have the same files that exist on the production servers.
 
+    The older ``ignore_errors`` option silently discards all errors when the loaded file
+    doesn't exist or contains invalid code.
+
+.. configuration-block::
+
+    .. code-block:: yaml
+
+        # config/services.yaml
+        imports:
+            - { resource: '/etc/sites/mysite.com/parameters.yaml', ignore_errors: true }
+
+        # ...
+
+    .. code-block:: xml
+
+        <!-- config/services.xml -->
+        <?xml version="1.0" encoding="UTF-8" ?>
+        <container xmlns="http://symfony.com/schema/dic/services"
+            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+            xsi:schemaLocation="http://symfony.com/schema/dic/services
+                https://symfony.com/schema/dic/services/services-1.0.xsd
+                http://symfony.com/schema/dic/symfony
+                https://symfony.com/schema/dic/symfony/symfony-1.0.xsd">
+
+            <imports>
+                <import resource="/etc/sites/mysite.com/parameters.yaml" ignore-errors="true"/>
+            </imports>
+
+            <!-- ... -->
+        </container>
+
+    .. code-block:: php
+
+        // config/services.php
+        use Symfony\Component\Config\Loader\FileLoader;
+
+        $loader->import('/etc/sites/mysite.com/parameters.yaml', null, FileLoader::IGNORE_ALL);
+
+        // ...
+
 As you've seen, there are lots of ways to organize your configuration files. You
 can choose one of these or even create your own custom way of organizing the
 files. For even more customization, see ":doc:`/configuration/override_dir_structure`".