Skip to content

Commit 277032f

Browse files
committed
minor #8603 Reworded the introduction of event listeners article (javiereguiluz)
This PR was merged into the 2.7 branch. Discussion ---------- Reworded the introduction of event listeners article We have an article explaining the kernel events, so there's no need to link to the KernelEvents class source code. Commits ------- be2f7ef Reworded the introduction of event listeners article
2 parents 26cf8bf + be2f7ef commit 277032f

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)