Guilhem Niot

@xabbuh Apparently the reason was bc (see [this comment](https://github.com/FriendsOfSymfony/FOSRestBundle/pull/257#discussion_r1113038)) so we can safely change it.

Hi! We could allow that indeed but it doesn't seem Symfony has a simple mechanism permitting that, it would probably require having our own merging strategy (by extending https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Config/Definition/VariableNode.php#L120). PR...

Sure, we could do that, but will it truly be useful ?

I don't think we should ignore all setters, they will be normalized by the Symfony serializer if you do nothing and hence should be documented imo. However, a solution could...

I think the issue is your input data, constructor arguments are entirely managed by symfony serializer. Did you actually put something under `domain` in your input?

This is not a supported case, the serializer doesn't know about other request parameters, the only solution I see is to deserialize your input by hand (with https://symfony.com/doc/current/components/serializer.html#handling-constructor-arguments).

Yes it isn't supported but PRs are welcome :)

You can use `@SWG\Property` to specify your property's type when it's not well detected, see https://symfony.com/doc/current/bundles/NelmioApiDocBundle/index.html#general-php-objects.

Sure why not, but probably more against `Ramsey\Uuid\Uuid`, right? (https://github.com/ramsey/uuid/blob/5.x/src/Uuid.php) `UuidInterface` really does not specify the serialization format so it would be weird in my opinion to add a describer...

Have you tried creating a jms handler to serialize your error as you wish?