Please sign in to comment.
bug #27292 [Serializer] Fix and improve constraintViolationListNormal…
…izer's RFC7807 compliance (dunglas) This PR was squashed before being merged into the 4.1 branch (closes #27292). Discussion ---------- [Serializer] Fix and improve constraintViolationListNormalizer's RFC7807 compliance | Q | A | ------------- | --- | Branch? | 4.1 | Bug fix? | yes | New feature? | no <!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | yes| Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | #22150 (comment) | License | MIT | Doc PR | todo This PR fixes and improves [RFC 7807](https://tools.ietf.org/html/rfc7807#section-3.2) compliance of `ConstraintViolationListNormalizer` (introduced in 4.1): * As recommended, use a specific namespace for Symfony validation error (`http://symfony.com/doc/current/validation.html`, because it already exists and gives information about the error. * Allow to set all properties defined in the RFC using the serialization context * Remove the `detail` key if no detail is provided (according to the spec) * Change the Symfony specific extension to use the same terminology than the RFC itself (type and title) * Use the proper `urn:uuid` scheme (RFC 4122) for the UUID code (more standard, and improve hypermedia capabilities). ping @teohhanhui Commits ------- 3c789c6 [Serializer] Fix and improve constraintViolationListNormalizer's RFC7807 compliance
- Loading branch information...
Showing with 31 additions and 14 deletions.