-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Serializer] #44283
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
Labels
Comments
This seems related to #44273. |
Can you please confirm #44295 fixes the issue? |
nicolas-grekas
added a commit
that referenced
this issue
Nov 28, 2021
…s-grekas) This PR was merged into the 4.4 branch. Discussion ---------- [Serializer] fix support for lazy/unset properties | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #44273 #44283 | License | MIT | Doc PR | - This basically backports #43469 into 4.4, which is the way to go to fix #44273. The code that exists to handle uninitialized properties is broken anyway (it was before the recent changes.) Commits ------- db043aa [Serializer] fix support for lazy/unset properties
Yes, it seems that patch fixes somehow 👍 when we can expect at 4.4? |
Patch releases are done once a month. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected
4.4.35
Description
After migrating from v4.4.31 to v4.4.35 broke some functionality for private variables.
How to reproduce
Occurs an error:
"class@anonymous/home/docker/sample/src/Sample.php:51$901a0->get__loaders() method not found"
because in previous version private variables was not supposed to be serialized
Possible Solution
No response
Additional Context
It most likely related to this commit because removed
but you can see full changes for this migration that arises error.
The text was updated successfully, but these errors were encountered: