feat(Serializer): update MissingConstructorArgumentsException message #5902
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Accidentally have closed #5649 PR
This is its copy.
Have found that if validation attributes are specified on DTOs or if the
Valid()
constraint is used on not api-resource property (just an entity in example) then Symfony's AbstractNormalizer is used and it has a bit differentMissingConstructorArgumentsException
exception message that also contains the list of missed arguments.But in ApiPlatform this exception has another message and it contains only the first one of missed arguments in it.
This way someone, who relies on this message, in example, to convert it to something like validation error in the response, will get different messages.
So I want to suggest to make this message and its parameters consistent with Symfony's one.
The example of the new message: