symfony
diff --git a/‎components/error_handler.rst
Lines changed: 6 additions & 30 deletions b/‎components/error_handler.rst
Lines changed: 6 additions & 30 deletions
diff --git a/‎components/polyfill_uuid.rst
Lines changed: 57 additions & 0 deletions b/‎components/polyfill_uuid.rst
Lines changed: 57 additions & 0 deletions
diff --git a/‎logging/monolog_email.rst
Lines changed: 5 additions & 0 deletions b/‎logging/monolog_email.rst
Lines changed: 5 additions & 0 deletions
diff --git a/‎routing.rst
Lines changed: 12 additions & 1 deletion b/‎routing.rst
Lines changed: 12 additions & 1 deletion
diff --git a/‎validation/custom_constraint.rst
Lines changed: 6 additions & 0 deletions b/‎validation/custom_constraint.rst
Lines changed: 6 additions & 0 deletions
@@ -22,14 +22,9 @@ Installation
 Usage
 -----
 
-The ErrorHandler component provides several tools to help you debug PHP code:
-
-* An **error handler** that turns PHP errors into exceptions;
-* An **exception handler** that turns uncaught PHP exceptions into nice PHP responses;
-* A **debug class loader** that provides better errors when a class is not found.
-
+The ErrorHandler component provides several tools to help you debug PHP code.
 Call this method (e.g. in your :ref:`front controller <architecture-front-controller>`)
-to enable all these features in your application::
+to enable all of them in your application::
 
     // public/index.php
     use Symfony\Component\ErrorHandler\Debug;
@@ -52,9 +47,10 @@ Turning PHP Errors into Exceptions
 ----------------------------------
 
 The :class:`Symfony\\Component\\ErrorHandler\\ErrorHandler` class catches PHP
-errors and turns them into PHP's :phpclass:`ErrorException` objects, except for
-fatal PHP errors, which are turned into Symfony's
-:class:`Symfony\\Component\\ErrorHandler\\Exception\\FatalErrorException` objects.
+errors and uncaught PHP exceptions and turns them into PHP's
+:phpclass:`ErrorException` objects, except for fatal PHP errors, which are
+turned into Symfony's :class:`Symfony\\Component\\ErrorHandler\\Exception\\FatalErrorException`
+objects.
 
 If the application uses the FrameworkBundle, this error handler is enabled by
 default in the :ref:`production environment <configuration-environments>`
@@ -120,26 +116,6 @@ wrap several function calls inside an anonymous function::
         return $data;
     });
 
-Debugging Uncaught PHP Exceptions
----------------------------------
-
-The :class:`Symfony\\Component\\ErrorHandler\\ExceptionHandler` class catches
-uncaught PHP exceptions and turns them into a nice response, so you can debug
-them. It is useful in :ref:`debug mode <debug-mode>` to replace the default
-PHP/XDebug output with something prettier and more useful.
-
-If the :doc:`HttpFoundation component </components/http_foundation>` is
-available, the handler returns a Symfony's
-:class:`Symfony\\Component\\HttpFoundation\\Response` object. Otherwise, it returns
-a generic PHP response.
-
-Use the following code (e.g. in your :ref:`front controller <architecture-front-controller>`)
-to enable this exception handler::
-
-    use Symfony\Component\ErrorHandler\ExceptionHandler;
-
-    ExceptionHandler::register();
-
 .. _component-debug-class-loader:
 
 Class Loading Debugger
 
@@ -0,0 +1,57 @@
+.. index::
+    single: Polyfill
+    single: PHP
+    single: Components; Polyfill
+
+The Symfony Polyfill / UUID Component
+=====================================
+
+    This component provides ``uuid_*`` functions to users who run PHP versions
+    without the UUID extension.
+
+Installation
+------------
+
+.. code-block:: terminal
+
+    $ composer require symfony/polyfill-uuid
+
+.. include:: /components/require_autoload.rst.inc
+
+Usage
+-----
+
+Once this component is installed in your application, you can use the following
+functions, no matter if the `PHP UUID extension`_ is installed or not in your
+server.
+
+Provided Constants
+~~~~~~~~~~~~~~~~~~
+
+* ``UUID_VARIANT_NCS`` (value = 0)
+* ``UUID_VARIANT_DCE`` (value = 1)
+* ``UUID_VARIANT_MICROSOFT`` (value = 2)
+* ``UUID_VARIANT_OTHER`` (value = 3)
+* ``UUID_TYPE_DEFAULT`` (value = 0)
+* ``UUID_TYPE_TIME`` (value = 1)
+* ``UUID_TYPE_DCE`` (value = 4)
+* ``UUID_TYPE_NAME`` (value = 1)
+* ``UUID_TYPE_RANDOM`` (value = 4)
+* ``UUID_TYPE_NULL`` (value = -1)
+* ``UUID_TYPE_INVALID`` (value = -42)
+
+Provided Functions
+~~~~~~~~~~~~~~~~~~
+
+* :phpfunction:`uuid_create`
+* :phpfunction:`uuid_is_valid`
+* :phpfunction:`uuid_compare`
+* :phpfunction:`uuid_is_null`
+* :phpfunction:`uuid_type`
+* :phpfunction:`uuid_variant`
+* :phpfunction:`uuid_time`
+* :phpfunction:`uuid_mac`
+* :phpfunction:`uuid_parse`
+* :phpfunction:`uuid_unparse`
+
+.. _`PHP UUID extension`: https://pecl.php.net/package/uuid
@@ -4,6 +4,11 @@
 How to Configure Monolog to Email Errors
 ========================================
 
+.. caution::
+
+    This feature is not compatible yet with the new :doc:`Symfony mailer </mailer>`,
+    so it requires using SwiftMailer.
+
 `Monolog`_ can be configured to send an email when an error occurs with an
 application. The configuration for this requires a few nested handlers
 in order to avoid receiving too many emails. This configuration looks
 
@@ -1165,6 +1165,8 @@ the common configuration using options when importing the routes.
             # An imported route with an empty URL will become "/blog/"
             # Uncomment this option to make that URL "/blog" instead
             # trailing_slash_on_root: false
+            # you can optionally exclude some files/subdirectories when loading annotations
+            # exclude: '../src/Controller/{DebugEmailController}.php'
 
     .. code-block:: xml
 
@@ -1178,11 +1180,13 @@ the common configuration using options when importing the routes.
             <!--
                 the 'prefix' value is added to the beginning of all imported route URLs
                 the 'name-prefix' value is added to the beginning of all imported route names
+                the 'exclude' option defines the files or subdirectories ignored when loading annotations
             -->
             <import resource="../src/Controller/"
                 type="annotation"
                 prefix="/blog"
-                name-prefix="blog_">
+                name-prefix="blog_"
+                exclude="../src/Controller/{DebugEmailController}.php">
                 <!-- these requirements are added to all imported routes -->
                 <requirement key="_locale">en|es|fr</requirement>
             </import>
@@ -1202,6 +1206,8 @@ the common configuration using options when importing the routes.
         use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;
 
         return function (RoutingConfigurator $routes) {
+            // use the optional fifth argument of import() to exclude some files
+            // or subdirectories when loading annotations
             $routes->import('../src/Controller/', 'annotation')
                 // this is added to the beginning of all imported route URLs
                 ->prefix('/blog')
@@ -1215,6 +1221,11 @@ the common configuration using options when importing the routes.
             ;
         };
 
+.. versionadded:: 4.4
+
+    The option to exclude some files or subdirectories when loading annotations
+    was introduced in Symfony 4.4.
+
 In this example, the route of the ``index()`` action will be called ``blog_index``
 and its URL will be ``/blog/``. The route of the ``show()`` action will be called
 ``blog_show`` and its URL will be ``/blog/{_locale}/posts/{slug}``. Both routes
 
@@ -85,13 +85,19 @@ The validator class is also simple, and only has one required method ``validate(
             }
 
             if (!preg_match('/^[a-zA-Z0-9]+$/', $value, $matches)) {
+                // the argument must be a string or an object implementing __toString()
                 $this->context->buildViolation($constraint->message)
                     ->setParameter('{{ string }}', $value)
                     ->addViolation();
             }
         }
     }
 
+.. versionadded:: 4.4
+
+    The feature to allow passing an object as the ``buildViolation()`` argument
+    was introduced in Symfony 4.4.
+
 Inside ``validate``, you don't need to return a value. Instead, you add violations
 to the validator's ``context`` property and a value will be considered valid
 if it causes no violations. The ``buildViolation()`` method takes the error