fix(symfony): remove redundant messenger dispatch docblocks#8410
Open
ousamabenyounes wants to merge 1 commit into
Open
fix(symfony): remove redundant messenger dispatch docblocks#8410ousamabenyounes wants to merge 1 commit into
ousamabenyounes wants to merge 1 commit into
Conversation
Member
|
can this target 4.3 ? Not sure the dispatch trait test is useful drop it please. |
ousamabenyounes
force-pushed
the
fix-8312-dispatch-trait-docblock
branch
from
July 23, 2026 11:15
9de133a to
771c789
Compare
Author
|
Addressed this in Changes:
Validation:
|
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
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.
Summary
The two Messenger
DispatchTraitimplementations declared@param object|Envelope $message. That union is redundant because the method already acceptsobject, andsymfony/type-inforejects unions combiningobjectwith a concrete class.This removes the redundant docblocks and adds a regression test that resolves any future
@param $messagedocblock type from both traits through TypeInfo with the trait import context.Local review
Reviewed before opening this PR. One test-risk finding was fixed before commit: the new regression test now records an assertion when a trait has no docblock or no
@param $message, avoiding a future risky-test path.Test verification (RED → GREEN)
RED, after adding the regression test on upstream
main:GREEN, with the fix:
Fix-reverted regression check:
Additional checks:
All commands were run inside ephemeral Docker containers with
docker run --rm -u "$(id -u):$(id -g)" -v "$PWD":/app -w /app composer:2 ....