Skip to content

Commit be2f7ef

Browse files
committed
Reworded the introduction of event listeners article
1 parent 069707a commit be2f7ef

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

event_dispatcher.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,10 @@ During the execution of a Symfony application, lots of event notifications are
99
triggered. Your application can listen to these notifications and respond to
1010
them by executing any piece of code.
1111

12-
Internal events provided by Symfony itself are defined in the
13-
:class:`Symfony\\Component\\HttpKernel\\KernelEvents` class. Third-party bundles
14-
and libraries also trigger lots of events and your own application can trigger
15-
:doc:`custom events </components/event_dispatcher>`.
12+
Symfony triggers several :doc:`events related to the kernel </reference/events>`
13+
while processing an HTTP Request, third-party bundles and libraries also trigger
14+
lots of events and your own application can trigger :doc:`custom events
15+
</components/event_dispatcher>`.
1616

1717
All the examples shown in this article use the same ``KernelEvents::EXCEPTION``
1818
event for consistency purposes. In your own application, you can use any event

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy