JMSSerializerBundle
JMSSerializerBundle copied to clipboard
schmittjoh
Easily serialize, and deserialize data of any complexity (supports XML, JSON, YAML)
| Q | A | ---------------- | ----- | Bug report? | yes | Feature request? | no | BC Break report? | no | RFC? | no ## Steps...
The `jms/serializer` supports php8 (on dev-master). It would be good to update this package as well.
Currently I need to use the serializer differently at one point in my application, would be excellent if we can declare a default serializer and others with different configurations Example...
Just upgraded from 2.x to 3.x and this is the error I get. It seems to be related to: ``` visitors: json_serialization: options: 0 # json_encode options bitmask, suggested JSON_PRETTY_PRINT...
| Q | A | ---------------- | ----- | Bug report? | yes After a migration sf3 => sf4 and a jms 2 =>3 upgrade, my project is not working...
I have to search Internet to get to know how to switch to **camelCase** from the default **snake_case**. This is probably the very first thing many developers are looking for,...
| Q | A | ---------------- | ----- | Bug report? | yes | Feature request? | no | BC Break report? | don't know | RFC? | no ##...
Feature request? yes It would be nice to be able to configure groups for deeper branches also in configuration. Currently this is only possible with direct calls: http://jmsyst.com/libs/serializer/master/cookbook/exclusion_strategies . For...
```JMS\Serializer\GraphNavigator\SerializationGraphNavigator::accept()``` line 204: If there's a handler given for the custom type, e.g. ```JMS\Serializer\Handler\FormErrorHandler``` to handle form errors, ```SerializationGraphNavigator::afterVisitingObject()``` is never called, so listeners of **serializer.post_serialize** are never notified. Is...
| Q | A | ------------- | --- | Bug fix? | no | New feature? | no | Doc updated | yes | BC breaks? | no | Deprecations?...
Metadata
Owner
Metadata
Easily serialize, and deserialize data of any complexity (supports XML, JSON, YAML)