feat(symfony): map UniqueConstraintViolationException to 422 by default - #8478
Merged
Merged
Conversation
VincentLanglet
approved these changes
Aug 31, 2026
Member
|
thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to the second point of #8405, where @soyuka concluded "Probably just a 422":
Doctrine\DBAL\Exception\UniqueConstraintViolationExceptionis now mapped to 422 in the defaultexception_to_status, next to the existingOptimisticLockException => 409. Referencing the class stays safe when the DBAL is not installed, like the existingOptimisticLockExceptionentry (::classdoes not load the class).The first point of the issue (merging user config with the defaults) is left out, per the same comment ("we won't change the behavior").