[Messenger] Document serializedTypeName option in AsMessage attribute - #21844
Merged
javiereguiluz merged 1 commit intoFeb 5, 2026
Merged
Conversation
OskarStark
reviewed
Feb 3, 2026
lacatoire
force-pushed
the
docs/messenger-custom-serialized-type
branch
from
February 3, 2026 09:42
5bf7179 to
0d07586
Compare
OskarStark
reviewed
Feb 3, 2026
javiereguiluz
force-pushed
the
docs/messenger-custom-serialized-type
branch
from
February 5, 2026 09:54
8c939b0 to
fac36d9
Compare
Member
|
A very nice contribution. I didn't change a single character while merging. Thanks! |
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 PR documents the new
serializedTypeNameoption of the#[AsMessage]attribute, introduced in Symfony 8.1.This option allows customizing the
typeheader of serialized messages, improving interoperability with non-Symfony applications or systems using different naming conventions.Fixes #21793