Asmir Mustafic

Calculating the highest row solves the issue. I think that it should be mentioned somewhere (docs?) that `AutoFilter` takes a ton of memory, and that it is recommended to keep...

I've read better the description for this ticket and seems something different, however I have created the fix for the issue I've encountered https://github.com/PHPOffice/PhpSpreadsheet/pull/3527

sorry for the late reply. makes sense what you are suggesting. would be happy to see a PR

Currently there are no ways to define different naming schemes when serializing/deserializing out of the box. You can implement https://github.com/schmittjoh/serializer/blob/1.x/src/JMS/Serializer/Naming/AdvancedNamingStrategyInterface.php and do it by your self by examining the Context.

Hi! Thanks for the contribution. Can you update the other visitors? (xml and yaml) Can you also update the documentation?

@rvadym I really like what @alcalyn did in https://github.com/alcalyn/serializer-doctrine-proxies unfortunately the solution is really specific and at the moment "incomplete"... as example: - all doctrine entities with be serialized with...

A possible api for the feature can be: ```php class User { /** * @var Post * @Type("DoctrineIdentifiers

Hi, thanks for the request. Currently there is nothing in the core that allows something similar. Maybe a pre/post serialization listener can do the work for you here...

`PropertyMetadata` gives you the type of data you are going to unserialize. from it you can infer what you need

:( handlers are always per "type"...