Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
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.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes fromall commits
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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. | ||
| 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>`. | ||
Member There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 | ||
| 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 | ||