@webmozart any idea how to solve this ?

@stof @webmozart Any update on this yet?

@tobias-93 The solution is to (a) configure your project to use the 2.5 API and (b) simply use the methods of the new interface. In order to circumvent IDE errors, you can add:

use Symfony\Component\Validator\Context\ExecutionContextInterface;

class MyValidator extends ConstraintValidator
{
    /**
     * @var ExecutionContextInterface
     */
    protected $context;

    // ...
}

to your constraint validator (or your project's base validator). Be aware that if you use the new methods, your code cannot be used with the <2.5 API anymore (obviously). So my recommendation is:

• use the new interface for 2.5+ projects/bundles
• use the old interface for bundles that should be compatible with <2.5

@webmozart are all core constraint validators written in a way support all APIs (i.e 2.4, 2.5-bc and 2.5) ? Or do they require enabling at least the legacy mode ?
same for bundles needing to continue to support the 2.3 LTS. Can they be compatible with 2.5 without legacy mode easily, or does it require big changes ?

@stof Currently, both the 2.5-bc and 2.5 APIs use the class LegacyExecutionContext. In this way the old validators can still use the old context API even with the 2.5 API.

However, I guess it would be wise to change this to use ExecutionContext in the 2.5 API so that our users can check whether they use the old API by just making the switch and checking for errors. We could fix the core validators by adding:

• LegacyAllValidator (and likewise for all validators that use the old API - shouldn't be many)
• LegacyConstraintValidatorFactory (to use the legacy validators)

@webmozart Thank you for your comments, I will adapt my project using your guideline.