…cked for uniqueness (wkania)This PR was squashed before being merged into the 6.1 branch.Discussion----------[Validator] Define which collection keys should be checked for uniqueness| Q             | A| ------------- | ---| Branch?       | 5.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       |Fix#9888| License       | MIT| Doc PR        |symfony/symfony-docs#16713Currently, the validator checks each element of the collection as a whole. We already have a custom normalizer (which is great), but it would be nice to be able to check for uniqueness certain [collection](https://symfony.com/doc/current/reference/constraints/Collection.html) keys.For example, some fields in the collection element can be identifiers. They should be unique within the collection, even when the rest of the element data are different.Current state:- validates that all the elements of the given collection are uniqueNew state:- preserve the current state,- all old tests pass (no changes in them),- no breaking changes,- define which collection fields should be checked for uniqueness (optional),- fields are optional in each element of the collection. Use [collection constraints](https://symfony.com/doc/current/reference/constraints/Collection.html) if they are requiredExamples:1. Basic example. Each translation of the same resource must be in a different language.```phpuse Symfony\Component\Validator\Constraints as Assert;/** *@Assert\Count(min=1), *@Assert\Unique(fields={"language"}), *@Assert\Collection( *         fields = { *             "language" = { *@Assert\NotBlank, *@Assert\Length(min = 2, max = 2), *@Assert\Language *             }, *             "title" = { *@Assert\NotBlank, *@Assert\Length(max = 255) *             }, *             "description" = { *@Assert\NotBlank, *@Assert\Length(max = 255) *             } *         } * ) */public array $translations = [];```2. An example where Optional is recognizable. Items with the id are changed and without are new.```phpuse Symfony\Component\Validator\Constraints as Assert;use Symfony\Component\Validator\Constraints\Optional;/** *@Assert\Unique(fields={"id"}), *@Assert\Collection( *         fields = { *             "id" =@Assert\Optional({ *@Assert\Uuid *             }), *             "name" = { *@Assert\NotBlank, *@Assert\Length(max = 255) *             } *         } * ) */public array $items = [];```3. An example with composite uniqueness```phpuse Symfony\Component\Validator\Constraints as Assert;/** *@Assert\Unique(fields={"latitude", "longitude"}), *@Assert\Collection( *         fields = { *             "latitude" = { *@Assert\NotBlank *             }, *             "longitude" = { *@Assert\NotBlank *             }, *             "poi" = { *@Assert\Length(max = 255) *             } *         } * ) */public array $coordinates = [];```Commits-------0e8f4ce [Validator] Define which collection keys should be checked for uniqueness

…cked for uniqueness (wkania)This PR was squashed before being merged into the 6.1 branch.Discussion----------[Validator] Define which collection keys should be checked for uniqueness| Q             | A| ------------- | ---| Branch?       | 5.4| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       | Fix #9888| License       | MIT| Doc PR        |symfony/symfony-docs#16713Currently, the validator checks each element of the collection as a whole. We already have a custom normalizer (which is great), but it would be nice to be able to check for uniqueness certain [collection](https://symfony.com/doc/current/reference/constraints/Collection.html) keys.For example, some fields in the collection element can be identifiers. They should be unique within the collection, even when the rest of the element data are different.Current state:- validates that all the elements of the given collection are uniqueNew state:- preserve the current state,- all old tests pass (no changes in them),- no breaking changes,- define which collection fields should be checked for uniqueness (optional),- fields are optional in each element of the collection. Use [collection constraints](https://symfony.com/doc/current/reference/constraints/Collection.html) if they are requiredExamples:1. Basic example. Each translation of the same resource must be in a different language.```phpuse Symfony\Component\Validator\Constraints as Assert;/** *@Assert\Count(min=1), *@Assert\Unique(fields={"language"}), *@Assert\Collection( *         fields = { *             "language" = { *@Assert\NotBlank, *@Assert\Length(min = 2, max = 2), *@Assert\Language *             }, *             "title" = { *@Assert\NotBlank, *@Assert\Length(max = 255) *             }, *             "description" = { *@Assert\NotBlank, *@Assert\Length(max = 255) *             } *         } * ) */public array $translations = [];```2. An example where Optional is recognizable. Items with the id are changed and without are new.```phpuse Symfony\Component\Validator\Constraints as Assert;use Symfony\Component\Validator\Constraints\Optional;/** *@Assert\Unique(fields={"id"}), *@Assert\Collection( *         fields = { *             "id" =@Assert\Optional({ *@Assert\Uuid *             }), *             "name" = { *@Assert\NotBlank, *@Assert\Length(max = 255) *             } *         } * ) */public array $items = [];```3. An example with composite uniqueness```phpuse Symfony\Component\Validator\Constraints as Assert;/** *@Assert\Unique(fields={"latitude", "longitude"}), *@Assert\Collection( *         fields = { *             "latitude" = { *@Assert\NotBlank *             }, *             "longitude" = { *@Assert\NotBlank *             }, *             "poi" = { *@Assert\Length(max = 255) *             } *         } * ) */public array $coordinates = [];```Commits-------0e8f4cefdb [Validator] Define which collection keys should be checked for uniqueness

…aint (wkania)This PR was merged into the 6.1 branch.Discussion----------[Validator] Add the fields option to the Unique constraintMaybe I will add an example of use.Commits-------dcbad67 Added basic examplecaf3e1f [Validator] Add the fields option to the Unique constraint

This PR was merged into the 6.1 branch.Discussion----------[Validator] Fix typo in the Unique constraint`@wouterj`  just a small fix related to the#16713 (comment)Commits-------3fd53b9 Fix typo in the Unique constraint