-
-
Notifications
You must be signed in to change notification settings - Fork 586
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
Upgraded 2.4 -> 3.4 / Symfony 4.3.3 #1112
Comments
Hi, Did you follow the instructions in the upgrading document https://github.com/schmittjoh/serializer/blob/master/UPGRADING.md? It is difficult to guess the issue... |
I read the upgrading instructions and I don't use those features. Just basic Object->JSON->Object type stuff. Nothing fancy. |
are you sure the naming strategy works correct? I see only the "description" field being deserialized... |
Boom! Fixed!! Fixed up the the YAML files and had to nuke the cache manually. Thanks for pointing me in the right direction! |
Source JSON to deserialize
Output
Getting an entire project up to date. Upgraded JMS serializer and now nested objects don't seem to be deserialized and are null/empty. The top level properties appear to be set just fine. I feel like I may be doing something wrong? I've tried adding @expose and setting @type just to see if that mattered. I've reset the JMS yaml config file to defaults.
So I have an Object with an array of nested Objects. This array is empty. JSON source hasn't changed. I've tried changing from lazy loading to eager loading.
The text was updated successfully, but these errors were encountered: