From c808036510ba95fb699599b99e40811890bd0dbc Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Wed, 15 Nov 2017 17:02:13 +0100 Subject: [PATCH] Improved the link to the Symfony events reference --- event_dispatcher.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/event_dispatcher.rst b/event_dispatcher.rst index b1440ae7913..151a92000e7 100644 --- a/event_dispatcher.rst +++ b/event_dispatcher.rst @@ -64,8 +64,8 @@ The most common way to listen to an event is to register an **event listener**:: Each event receives a slightly different type of ``$event`` object. For the ``kernel.exception`` event, it is :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseForExceptionEvent`. - To see what type of object each event listener receives, see :class:`Symfony\\Component\\HttpKernel\\KernelEvents` - or the documentation about the specific event you're listening to. + Check out the :doc:`Symfony events reference ` to see + what type of object each event provides. Now that the class is created, you just need to register it as a service and notify Symfony that it is a "listener" on the ``kernel.exception`` event by