Skip to content

Reworded the introduction of event listeners article #8603

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
Nov 10, 2017
Merged

Reworded the introduction of event listeners article #8603

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
8 changes: 4 additions & 4 deletions event_dispatcher.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,10 @@ During the execution of a Symfony application, lots of event notifications are
triggered. Your application can listen to these notifications and respond to
them by executing any piece of code.

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this... but this sentence is too long. I think we need a period after HTTP Request. And then maybe the next sentence needs a little bit of work.


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