Remove ErrorRenderer reference everywhere

yceruto · yceruto · commit 9457979ba708 · 2019-11-26T08:47:40.000-05:00
diff --git a/components/error_handler.rst b/components/error_handler.rst
@@ -67,11 +67,6 @@ to enable this error handler::
 
     ErrorHandler::register();
 
-.. tip::
-
-    If you want to get even better exception pages, install the
-    :doc:`ErrorRenderer component </components/error_renderer>` too.
-
 Catching PHP Function Errors and Turning Them into Exceptions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -145,11 +140,6 @@ to enable this exception handler::
 
     ExceptionHandler::register();
 
-.. tip::
-
-    If you want to get even better exception pages, install the
-    :doc:`ErrorRenderer component </components/error_renderer>` too.
-
 .. _component-debug-class-loader:
 
 Class Loading Debugger
diff --git a/components/error_renderer.rst b/components/error_renderer.rst
diff --git a/components/http_kernel.rst b/components/http_kernel.rst
@@ -554,7 +554,7 @@ below for more details).
     The listener has several goals:
 
     1) The thrown exception is converted into a
-       :class:`Symfony\\Component\\ErrorRenderer\\Exception\\FlattenException`
+       :class:`Symfony\\Component\\ErrorHandler\\Exception\\FlattenException`
        object, which contains all the information about the request, but which
        can be printed and serialized.
 
diff --git a/controller/error_pages.rst b/controller/error_pages.rst
@@ -247,7 +247,7 @@ the request that will be dispatched to your controller. In addition, your contro
 will be passed two parameters:
 
 ``exception``
-    A :class:`\\Symfony\\Component\\ErrorRenderer\\Exception\\FlattenException`
+    A :class:`\\Symfony\\Component\\ErrorHandler\\Exception\\FlattenException`
     instance created from the exception being handled.
 
 ``logger``
diff --git a/create_framework/http_kernel_httpkernel_class.rst b/create_framework/http_kernel_httpkernel_class.rst
@@ -69,7 +69,7 @@ Our code is now much more concise and surprisingly more robust and more
 powerful than ever. For instance, use the built-in ``ExceptionListener`` to
 make your error management configurable::
 
-    $errorHandler = function (Symfony\Component\ErrorRenderer\Exception\FlattenException $exception) {
+    $errorHandler = function (Symfony\Component\ErrorHandler\Exception\FlattenException $exception) {
         $msg = 'Something went wrong! ('.$exception->getMessage().')';
 
         return new Response($msg, $exception->getStatusCode());
@@ -91,7 +91,7 @@ The error controller reads as follows::
     // example.com/src/Calendar/Controller/ErrorController.php
     namespace Calendar\Controller;
 
-    use Symfony\Component\ErrorRenderer\Exception\FlattenException;
+    use Symfony\Component\ErrorHandler\Exception\FlattenException;
     use Symfony\Component\HttpFoundation\Response;
 
     class ErrorController
