You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR was merged into the 6.2 branch.
Discussion
----------
[Messenger] Fix `TransportNamesStamp` deserialization
| Q | A
| ------------- | ---
| Branch? | 6.2
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | #49574, #31490 (comment)
| License | MIT
| Doc PR | n/a
Currently, when ones use `TransportNameStamp` the following exception can occur if they don't use native PHP serialization:
```
In Serializer.php line 125:
[Symfony\Component\Messenger\Exception\MessageDecodingFailedException]
Could not decode stamp: Cannot create an instance of "Symfony\Component\Messenger\Stamp\TransportNamesStamp" from serialized data because its constructor requires parameter "transports" to be present.
In AbstractNormalizer.php line 384:
[Symfony\Component\Serializer\Exception\MissingConstructorArgumentsException]
Cannot create an instance of "Symfony\Component\Messenger\Stamp\TransportNamesStamp" from serialized data because its constructor requires parameter "transports" to be present.
```
This PR renames `TransportNamesStamp` constructor argument in order to match the accessor method (`getTransportNames`) so that deserialization works when using the Serializer.
I know this is technically a (small) BC break but Symfony's BC does not cover named arguments if I remember correctly.
Commits
-------
2c7eee0 [Messenger] Fix TransportNamesStamp deserialization
0 commit comments