-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Mime] Make RawMessage::message nullable in the constructor #53674
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
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 |
Can you please add a test case that reproduces the issue you're seeing in the linked issue? |
Done @nicolas-grekas. I reused an existing test as the previous extractor didn't make too much sense anyway because there was no PHPDoc in the FYI I rebased the fix on |
Did that trigger the failure? |
I tried to add a dedicated minimal test that shows my issue. The pipelines are failing but at least it gives an idea. Any ideas how we should proceed on this? I am new to contributing to Symfony, hence I feel a bit lost. |
Thanks for pointing that out @smnandre. I rebased it on There the underlying I guess I still need to rework the new test, at least rename it more meaningfully, this was just a quick approach to showcase my issue. What do you think @nicolas-grekas ? |
I dug the issue a bit and I submitted #53678 instead: the property shouldn't accept null in the first place, and the serializer shouldn't generate null messages. |
The
RawMessage::message
is nullable. However the parameter passed to the constructor is not allowed to benull
.