-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Doctrine Bridge] document priority for doctrine.event_listener tag #9944
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -271,3 +271,57 @@ to the tag like so: | |
|
||
.. _`The Event System`: http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/events.html | ||
.. _`the Doctrine Documentation`: https://symfony.com/doc/current/bundles/DoctrineBundle/entity-listeners.html | ||
|
||
|
||
8000 | Priorities for Event Listeners | |
------------------------------ | ||
|
||
In case you have multiple listeners for the same event you can control the order | ||
in which they are invoked using the ``priority`` attribute on the tag. | ||
Listeners with a higher priority are invoked first. | ||
|
||
.. configuration-block:: | ||
|
||
.. code-block:: yaml | ||
|
||
services: | ||
my.listener.with_high_priority: | ||
class: AppBundle\EventListener\MyHighPriorityListener | ||
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. This is not the scope of this PR but I don't think we should use the same namespace for kernel listener and doctrine listener (like form listeners should remain in |
||
tags: | ||
- { name: doctrine.event_listener, event: postPersist, priority: 10 } | ||
|
||
my.listener.with_low_priority: | ||
class: AppBundle\EventListener\MyLowPriorityListener | ||
tags: | ||
- { name: doctrine.event_listener, event: postPersist, priority: 1 } | ||
|
||
.. code-block:: xml | ||
|
||
<?xml version="1.0" ?> | ||
<container xmlns="http://symfony.com/schema/dic/services" | ||
xmlns:doctrine="http://symfony.com/schema/dic/doctrine"> | ||
|
||
<services> | ||
<service id="my.listener.with_high_priority" class="AppBundle\EventListener\MyHighPriorityListener"> | ||
<tag name="doctrine.event_listener" event="postPersist" priority="10" /> | ||
</service> | ||
<service id="my.listener.with_low_priority" class="AppBundle\EventListener\MyLowPriorityListener"> | ||
<tag name="doctrine.event_listener" event="postPersist" priority="1" /> | ||
</service> | ||
</services> | ||
</container> | ||
|
||
.. code-block:: php | ||
|
||
use AppBundle\EventListener\MyHighPriorityListener; | ||
use AppBundle\EventListener\MyLowPriorityListener; | ||
|
||
$container | ||
->register('my.listener.with_high_priority', MyHighPriorityListener::class) | ||
->addTag('doctrine.event_listener', array('event' => 'postPersist', 'priority' => 10)) | ||
; | ||
|
||
$container | ||
->register('my.listener.with_low_priority', MyLowPriorityListener::class) | ||
->addTag('doctrine.event_listener', array('event' => 'postPersist', 'priority' => 1)) | ||
; |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we please keep the naming convention here? e.g, using
app.listener.high_priority
? I would also removeMy
prefix on class names, I don't think we use such names elsewhere in the docs.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually followed the naming convention (for the service id) of the other examples in this file 😉
If you want I can rename all of them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, as this targets 2.8 why not, but then this would better be done in another PR. Let's wait for other maintainers opinion before making this change. Thanks!