-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[Serializer] Fix dealing with asymmetric visilibity for properties #61571
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
[Serializer] Fix dealing with asymmetric visilibity for properties #61571
Conversation
559a53e to
a91d37e
Compare
protected(set) propertiesprotected(set) or private(set) properties
|
I think (though I might be wrong) that the pipeline errors are not relevant in the context of this PR. |
nicolas-grekas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for opening this!
src/Symfony/Component/Serializer/Normalizer/ObjectNormalizer.php
Outdated
Show resolved
Hide resolved
a91d37e to
7407d03
Compare
|
Hi 😊 I hope you're doing well! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On closer review, this makes me think we also need to fix the call to isReadOnly in ReflectionExtractor on L365 - we might need to check for asym there also. Can you have a look?
src/Symfony/Component/Serializer/Normalizer/ObjectNormalizer.php
Outdated
Show resolved
Hide resolved
7407d03 to
81f3a04
Compare
Thanks for pointing that out! Maybe I’m wrong, but I think it might not be necessary to update the call to |
protected(set) or private(set) properties…otected(set)` properties
81f3a04 to
6310c44
Compare
|
Thank you @santysisi. |
Description
This PR resolves a crash in the
Serializerwhen deserializing an object with aprotected(set)orprivate(set)property