You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to handle Symfony\Component\Messenger\Exception\ValidationFailedException the same way, so that a conversion step isn’t needed? Or should the ValidationMiddleware throw Symfony\Component\Validator\Exception\ValidationFailedExceptions?
The text was updated successfully, but these errors were encountered:
…ut Messenger’s `ValidationFailedException` (MatTheCat)
This PR was merged into the 6.4 branch.
Discussion
----------
[Serializer] Make `ProblemNormalizer` give details about Messenger’s `ValidationFailedException`
| Q | A
| ------------- | ---
| Branch? | 6.4
| Bug fix? | no
| New feature? | yes
| Deprecations? | no
| Tickets | Fix#51739
| License | MIT
This PR fixes#51739 by handling `Symfony\Component\Messenger\Exception\ValidationFailedException` in the `ProblemNormalizer`.
Commits
-------
43240ab [Serializer] Make `ProblemNormalizer` give details about Messenger’s `ValidationFailedException`
Description
The
validation
middleware throwsSymfony\Component\Messenger\Exception\ValidationFailedException
s. You can map them to a 400 status code, but violations won’t be part of the response because theProblemNormalizer
will only considerSymfony\Component\Validator\Exception\ValidationFailedException
.Would it be possible to handle
Symfony\Component\Messenger\Exception\ValidationFailedException
the same way, so that a conversion step isn’t needed? Or should theValidationMiddleware
throwSymfony\Component\Validator\Exception\ValidationFailedException
s?The text was updated successfully, but these errors were encountered: