Skip to content

Fix priority range values for event listeners. #5194

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
wants to merge 3 commits into from
Closed
Changes from all commits
Commits
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
5 changes: 2 additions & 3 deletions cookbook/service_container/event_listener.rst
Original file line number Diff line number Diff line change
Expand Up @@ -96,9 +96,8 @@ using a special "tag":
.. note::

There is an additional tag option ``priority`` that is optional and defaults
to 0. This value can be from -255 to 255, and the listeners will be executed
in the order of their priority (highest to lowest). This is useful when
you need to guarantee that one listener is executed before another.
to 0. The listeners will be executed in the order of their priority (highest to lowest).
This is useful when you need to guarantee that one listener is executed before another.

Request Events, Checking Types
------------------------------
Expand Down