Asmir Mustafic

This is most likely related to some type mapping error, like some entities have a type "array" but in reality they are doctrine collections. Days ago this https://github.com/schmittjoh/JMSSerializerBundle/issues/596 was solved....

I think that the best thing to do here is to have built-in handlers to run with a lower priority than the user defined one, in this way there is...

hi! If someone is interested, I'm working on a little tool that generates JMS metadata starting from an XSD definition... https://github.com/goetas/xsd2php#serilize--unserialize Any suggestion will be helpful :)

@trickreich I never had an use case for it (both serialization and deserialization)... not really planned. Obviously a PR from somebody else is welcome.

I see... effectively the features you are using are available only when serializing.

I'm not an expert of phpstan, how can be fixed this?

https://github.com/goetas/jms-serializer-phpstan-extension should fix it once for all I plan to release the 1.x in the next few days

if you have a look here https://github.com/schmittjoh/serializer/blob/master/src/JMS/Serializer/Construction/DoctrineObjectConstructor.php#L82 it is implemented as you need. can you share your object metadata?

```json { "articles": [ { "id": 1 }, { "id": 2 }, { "id": 3 } ], "client": { "id": 43 } } ``` works already and ```json { "articles":...

> I just added an empty handler and deserialization doesn't work at all. Maybe I missed something? can you elaborate?