… (lyrixx)This PR was merged into the 4.1-dev branch.Discussion----------[Serializer] Added a ConstraintViolationListNormalizer| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#11309| License       | MIT| Doc PR        | ----It seems logical to me that Symfony is able to serialise natively some very common Symfony data structure. (and requested by@nicolas-grekas &@javiereguiluz )Usage example (from symfony/symfony-demo):```php    /**     *@route("", name="api_blog_new")     *@method("POST")     * @Security("is_granted('ROLE_ADMIN')")     */    public function newAction(Request $request)    {        $data = $request->getContent();        $post = $this->get('serializer')->deserialize($data, Post::class, 'json', ['groups' => ['post_write']]);        $post->setAuthor($this->getUser());        $violations = $this->get('validator')->validate($post);        $post->setSlug($this->get('slugger')->slugify($post->getTitle()));        if (count($violations) > 0) {            $repr = $this->get('serializer')->serialize($violations, 'json');            return JsonResponse::fromJsonString($repr, 400);        }        $this->getDoctrine()->getManager()->persist($post);        $this->getDoctrine()->getManager()->flush();        $repr = $this->get('serializer')->serialize($post, 'json', ['groups' => ['post_read']]);        return JsonResponse::fromJsonString($repr);    }```Commits-------2a35d09 [Serializer] Added a ConstraintViolationListNormalizer

…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     <!-- seehttps://symfony.com/bc -->| Deprecations? | yes| Tests pass?   | yes    <!-- please add some, will be required by reviewers -->| Fixed tickets |#22150 (comment)| License       | MIT| Doc PR        | todoThis 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@teohhanhuiCommits-------3c789c6 [Serializer] Fix and improve constraintViolationListNormalizer's RFC7807 compliance