Yaroslav Yaremenko

1. Install from here https://github.com/yyaremenko/symfony-bugs-component-property-access 2. Run phpunit test: FAILURE (Comments are not added to the user) 3. Uncomment this method, as advised: https://github.com/yyaremenko/symfony-bugs-component-property-access/blob/c366b77c983ad41c009209a0681bc948f3d1ab92/src/Model/User.php#L22 4. Run phpunit test: SUCCESS (Comments...

Any update? Also, just to specify the problematic starting place: Symfony\Component\PropertyInfo\Extractor\ReflectionExtractor::$defaultArrayMutatorPrefixes

yep, still relevant

HI @WebMamba, I am afraid the problem has nothing to do with any sort of validation, please consider having a look at the mini project I gave a link to,...

@xabbuh I could try to make a fix, but it would be nice to know in advance what behavior is expected? should there be a root-level \Exception trhown? or Some\Specific\Exception?...

thank you for the quick reply, yes, I see your point; I would gladly update the docs, but, as I described here https://github.com/FriendsOfSymfony/FOSRestBundle/pull/2166 there are currently no docs regarding routing...

okay, I see, thank you for the info

@codr86 @tarjei you guys actually doomed yourself: bundle developers say you can never rely on (you can not extend) **FOS\RestBundle\Serializer\Normalizer\FormErrorHandler** https://github.com/FriendsOfSymfony/FOSRestBundle/issues/2240#issuecomment-640274425 > Additionally, these classes are tagged as internal so...

For those who may come across this post with the same problem **1. Create a decorator over JMS\Serializer\Handler\FormErrorHandler** example: ```php namespace App\Decorator; use JMS\Serializer\Handler\FormErrorHandler as JMSFormErrorHandler; use JMS\Serializer\Handler\SubscribingHandlerInterface; use JMS\Serializer\JsonSerializationVisitor;...

hi @xabbuh, thank you for the prompt reply; yes, I can confirm now - the links are no longer available on the website (though they were available by the moment...