#108013Support domain based language labels in ConstraintDecoratingValidator
Description
Currently it is hardcoded to to check if the string starts with LLL:
Reviews 1
History 24
-
Georg Ringer changed status
NewAccepted <span data-processor="relativetime" data-value="2026-02-07T06:40:59+00:00" > 02/07/26, 06:40 </span> -
Gerrit Code Review pushed patch set 1 for main to change 97648 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2026-11-14T13:58:56+00:00" > 11/14/26, 13:58 </span> -
Gerrit Code Review pushed patch set 2 for main to change 97648 <span data-processor="relativetime" data-value="2026-11-20T19:45:25+00:00" > 11/20/26, 19:45 </span>
Extbase
AbstractValidatoralso checks for theLLL:syntax and I currently have no good idea on how to support the new domain based language labels in extbase validators.Extbase validators do not require require a language file and developers can also just provide a custom string, which is not processed by
LocalizationServiceat all.Example from #102326 RST file:
#[Extbase\Validate([ 'validator' => 'Float', 'options' => [ 'message' => 'A custom, non translatable message', ], ])] protected float $myProperty = 0.0;Here, the
messageoption is uses as is for the validation error message, when the validator fails. When the validation message starts withLLL:, the validator “knows” that the string needs the be handled byLocalizationService.If we want to support domain based language labels in extbase validators, we could:
LocalizationService. IMO not an option, since not everyone uses localization files in projects