-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Messenger] Fix default serializer not handling DateTime objects properly #47702
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
[Messenger] Fix default serializer not handling DateTime objects properly #47702
Conversation
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
Hey! Oh no, it looks like you have made this PR towards a branch that is not maintained anymore. :/ Cheers! Carsonbot |
7b26e95
to
84e1379
Compare
Hey @barton-webwings, Thanks for your PR! As you can see in the Symfony releases calendar, the 4.3 version isn't maintained anymore, can you please target 4.4 instead? |
Hello @mtarld, yeah, the bot warned me about it too, so I rebased the branch onto symfony:4.4 and changed the target. I am getting some weird failures in the tests though, looks like due to direct float comparison. |
Don't worry about the failures, they are not related to your change. |
If you can, you could rebase your changes onto the latest |
84e1379
to
302b147
Compare
302b147
to
85c459c
Compare
Thank you @barton-webwings. |
I was using messenger standalone and needed to send messages in JSON format. While trying to do so using the Serializer class, I noticed that DateTime objects (present for example in RedeliveryStamp) are not serialized properly.
I fixed it by adding the proper normalizer.
I encountered it in version 5.2, but it should be applicable from version 4.4.
Before:
After: