[Messenger] Clarify sequential execution of handlers using priority#21631
Merged
javiereguiluz merged 2 commits intosymfony:6.4from Feb 12, 2026
Merged
[Messenger] Clarify sequential execution of handlers using priority#21631javiereguiluz merged 2 commits intosymfony:6.4from
javiereguiluz merged 2 commits intosymfony:6.4from
Conversation
ckrack
reviewed
Feb 6, 2026
Contributor
ckrack
left a comment
ckrack
left a comment
There was a problem hiding this comment.
Added a suggestion to avoid a ; in the sentence.
I think this targets the wrong branch, handler priority was not introduced in 8.0
Clarify the behavior of message handlers with priority.
javiereguiluz
force-pushed
the
patch-1
branch
from
9548718 to
e668895
Compare
Member
|
I like this proposal! It clarifies an important detail. Thanks Saidi ... and sorry it took us so long to merge this. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This clarification improves developer understanding of handler priority behavior.
Thanks in advance for your review!