Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
[WIP] Reorganize the Serializer documentation#6428
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| As a final result, the deserializer uses the ``first_name`` attribute as if | ||
| it were ``firstName`` and uses the ``getFirstName`` and ``setFirstName`` methods. | ||
| Using Callbacks to Serialize Properties with Object Instances |
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.
this should be moved to other chapters rather than removed
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.
Yes, I plan to move it to the normalizer doc ;-)
da8a235 to2d4ff3bCompareGuilhemN commentedApr 4, 2016
I wrote the doc about encoders. |
The aim of this PR is to split the Serializer component documentation into smaller articles: the encoders and the normalizers will have their own dedicated section.
The encoders documentation won't be necessary for everyone but it is always good to understand how they work. For example, I don't think that a lot of people knows that the
XmlEncoderconsiders keys beginning with@as attributes.The
JsonEncoderisn't really complex but it may be useful to know that it is based on the built in methodsjson_encodeandjson_decode.The documentation about normalizers is much more needed as they are a great feature not much documented for now. The
ObjectNormalizer(or theGetSetMethodNormalizerfor the 2.3 branch) is enough in most of the cases but sometimes people want something even more powerful and could use custom normalizers if they knew more about them.So please tell me if you like this reorganization and if you see anything to change before I start writing the sections about normalizers and encoders :-)