@webmozart given that you closed/replaced the PR I made (#7276) over a year and half ago after 6+ months on revision, would you mind answering me one question?

How could I use this new PR to assign a code to a ConstraintViolation? The problem still exists imho, as you can't use the code property that still can be found on ConstraintViolation.php

@aeoris You shouldn't. The code property is internal and meant for another purpose (namely internal validation codes).

@aeoris In fact, your PR contained two different things:

1. it exposed the "code" property so a user could override it
2. it set the internal violation codes I was talking about

The first point is solved by the generic "payload" property. The second point is partially solved by the new $violation->getConstraint() accessor. Now there are cases where a constraint validator can fail due to multiple reasons (see Length for example). In those cases, getCode() should return an appropriate error code - which you implemented in your PR.

I'll reapply your PR so that we can merge the interesting parts of it. :) Thanks again for your work!

This needs to be covered by some tests (to ensure that all mapping loaders are supporting it properly for instance).
Otherwise, this is a great idea

@stof Sure? Isn't passing options to constraints covered sufficiently already?

hmm, yeah, indeed.

The test fail is unrelated.

ping @symfony/deciders

👍

Thank you @webmozart.

@aeoris See #12021