Skip to content

Remove ErrorRenderer reference everywhere #12702

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 9, 2019
Merged

Remove ErrorRenderer reference everywhere #12702

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions components/error_handler.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down Expand Up @@ -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
Expand Down
159 changes: 0 additions & 159 deletions components/error_renderer.rst
View file
Open in desktop

This file was deleted.

2 changes: 1 addition & 1 deletion components/http_kernel.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion controller/error_pages.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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``
Expand Down
4 changes: 2 additions & 2 deletions create_framework/http_kernel_httpkernel_class.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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());
Expand All @@ -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
Expand Down