Asmir Mustafic

```json { "articles": [1, 2, 3 ], "client": 43 } ``` will not work out of the box (different hacks and tricks are necessary to make it work...) I see...

@MadeRelevant Thanks for spending your time to comment on this issue. As this in an open-source project, developed in my free time, I try to do my best to keep...

hmm, this is weird. the uses case covered by that piece of code should handle this situation: ```php class MyEntity { /** * @Serializer\Type("SOME_INTENTIONAL_WRONG_CLASS_NAME_USED_FOR_A_TYPE_HANDLER") */ private OtherEntity $composition; } ```...

the mentioned interface was meant only for few usecases (and that is why is makred as internal), the `SerializationVisitorInterface` and `DeserializationVisitorInterface` are the one that should be used more often....

> Maybe it's better to overwrite the getVisitor() method in each Event to specify the more specific interface (e.g. SerializationVisitorInterface) as return type. That would remove the need to check...

Not really fun of it, I prefer explicit types. Closing. If someone has valid points, i'm ready to re-consider it.

When typed properties will land in PHP, the `@var` annotation will be obsolete, then inferring the type from the property reflection will make perfectly sense. In that case will be...

Alright, I see that this feature has people that could use it. There are still many questions to be answered on how to implement it, some are: - should this...

implemented as separate driver, sounds a good idea to me!

TBH i do not see a value in this, it was intentionally disabled that sniff (and phpstorm automatically uses the multiline version...)