This is the wrong way to solve it. We must have 2 implementations, to be compatible with the 2.4 API as well.

It is exact, sorry. I will create Symfony\Bridge\Doctrine\Validator\Const raints\LegacyUniqueEntityValidator .
But what is the best solution to fix LegacyConstraintValidatorFactory ? (The most clean solution because the validator namespace is different)

For tests, I am not sure: I can create LegacyUniqueEntityValidator2Dot4ApiTest.php and LegacyUniqueEntityValidatorLegacyApiTest.php. But how fix UniqueValidatorTest ?

Thanks

Hi @hlecorche! To fix this issue, it is necessary to refactor UniqueValidatorTest and create separate tests as in the Validator component. I'm working on this as I'd like to get the fix out ASAP.

Ok thanks @webmozart

@webmozart given that this validator is registered as a sevrice in the different Doctrine bundles, you will have to do some changes in these bundles as well to change the class of the service based on the API version being used (which may be difficult when it is set to auto btw)

Replaced by #11582.

@stof Which bundles do you mean?

DoctrineBundle, DoctrineMongoDBBundle, DoctrinePHPCRBundle and DoctrinecouchDBBundle, i.e. all bundles registering an instance of the UniqueEntityValidator as service with the corresponding registry as argument

Fortunately that won't be necessary then. :)