…ption for denormalization (Nek-)This PR was squashed before being merged into the 4.1-dev branch (closes #25493).Discussion----------[Serializer] `default_constructor_arguments` context option for denormalization| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | (there is no RFC for this)| License       | MIT| Doc PR        |symfony/symfony-docs#8914## ProblemsIn the case you want to deserialize value-objects, if all the data required by its constructor are **not** given as input, the serializer will throw a simple `RuntimeException` exception. This makes impossible to catch it. (as current fix on my projects I use exception message to be sure to catch the good one X.x")The second problem is a missing feature to fill the required object with an empty one. This needs to be defined by the user because the serializer can't guess how to build it.Here is a project that exposes the problem of the current behavior.https://github.com/Nek-/api-platform-value-object## Solutions suggestedI suggest a solution in 2 parts because the second part is more touchy.1. Replace the current exception by a new specific one2. Add a new `empty_data` option to the context of deserialization so you can specify data for objects impossible to instantiate, this is great because the serializer no more throw exception and the validator can then work as expected and send violations to the user. This solution is inspired by forms solutions to fix the issue with value objectsHere is what you can do with this feature:```phpclass DummyValueObject{    public function __construct($foo, $bar) { $this->foo = $foo; $this->bar = $bar; }}$empty = new DummyValueObject('', '');$result = $normalizer->denormalize(['foo' => 'Hello'], DummyValueObject::class, 'json', [    'empty_data' => [        DummyValueObject::class => $empty,    ],]);// It's impossible to construct a DummyValueObject with only "foo" value. So the serializer// will replace it with the given empty data```There are 2 commits so I can quickly provide you only the first point if you want. Hope you'll like this.## Solution after discussion1. New exception `MissingConstructorArgumentsException`2. New context option `default_constructor_arguments````phpclass DummyValueObject{    public function __construct($foo, $bar) { $this->foo = $foo; $this->bar = $bar; }}$result = $normalizer->denormalize(['foo' => 'Hello'], DummyValueObject::class, 'json', [    'default_constructor_arguments' => [        DummyValueObject::class => ['foo' => '', 'bar' => ''],    ],]);// DummyValueObject is contructed with the given `foo` and empty `bar````Commits-------1523a85542 [Serializer]  context option for denormalization

…ption for denormalization (Nek-)This PR was squashed before being merged into the 4.1-dev branch (closes#25493).Discussion----------[Serializer] `default_constructor_arguments` context option for denormalization| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | (there is no RFC for this)| License       | MIT| Doc PR        |symfony/symfony-docs#8914## ProblemsIn the case you want to deserialize value-objects, if all the data required by its constructor are **not** given as input, the serializer will throw a simple `RuntimeException` exception. This makes impossible to catch it. (as current fix on my projects I use exception message to be sure to catch the good one X.x")The second problem is a missing feature to fill the required object with an empty one. This needs to be defined by the user because the serializer can't guess how to build it.Here is a project that exposes the problem of the current behavior.https://github.com/Nek-/api-platform-value-object## Solutions suggestedI suggest a solution in 2 parts because the second part is more touchy.1. Replace the current exception by a new specific one2. Add a new `empty_data` option to the context of deserialization so you can specify data for objects impossible to instantiate, this is great because the serializer no more throw exception and the validator can then work as expected and send violations to the user. This solution is inspired by forms solutions to fix the issue with value objectsHere is what you can do with this feature:```phpclass DummyValueObject{    public function __construct($foo, $bar) { $this->foo = $foo; $this->bar = $bar; }}$empty = new DummyValueObject('', '');$result = $normalizer->denormalize(['foo' => 'Hello'], DummyValueObject::class, 'json', [    'empty_data' => [        DummyValueObject::class => $empty,    ],]);// It's impossible to construct a DummyValueObject with only "foo" value. So the serializer// will replace it with the given empty data```There are 2 commits so I can quickly provide you only the first point if you want. Hope you'll like this.## Solution after discussion1. New exception `MissingConstructorArgumentsException`2. New context option `default_constructor_arguments````phpclass DummyValueObject{    public function __construct($foo, $bar) { $this->foo = $foo; $this->bar = $bar; }}$result = $normalizer->denormalize(['foo' => 'Hello'], DummyValueObject::class, 'json', [    'default_constructor_arguments' => [        DummyValueObject::class => ['foo' => '', 'bar' => ''],    ],]);// DummyValueObject is contructed with the given `foo` and empty `bar````Commits-------1523a85 [Serializer]  context option for denormalization

…uiluz)This PR was merged into the 4.1 branch.Discussion----------Add new serializer empty_data feature docThis is the documentation related to the following feature:symfony/symfony#25493Commits-------9f31bbb Fix not precise enough sentenceb0d3fe8 Minor reword5a48201 Add new serializer empty_data feature doc