Issue Bug Under Review

#108013Support domain based language labels in ConstraintDecoratingValidator

Lina Wolf 11/09/25, 10:47 updated 11/20/26, 19:45

Description

Currently it is hardcoded to to check if the string starts with LLL:

Reviews 1

History 24

  1. Torben Hansen commented <span data-processor="relativetime" data-value="2026-02-07T08:50:22+00:00" > 02/07/26, 08:50 </span>

    Extbase AbstractValidator also checks for the LLL: 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 LocalizationService at all.

    Example from #102326 RST file:

        #[Extbase\Validate([
            'validator' => 'Float',
            'options' => [
                'message' => 'A custom, non translatable message',
            ],
        ])]
        protected float $myProperty = 0.0;

    Here, the message option is uses as is for the validation error message, when the validator fails. When the validation message starts with LLL:, the validator “knows” that the string needs the be handled by LocalizationService.

    If we want to support domain based language labels in extbase validators, we could:

    • Deprecate the possibility to provide a custom string which is not handled by LocalizationService. IMO not an option, since not everyone uses localization files in projects
    • Introduce a new prefix for domain based language labels in
    • Try to determine, if we have a domain based language labels via code (e.g. check for syntax – no spaces in string)
  2. Gerrit Code Review pushed patch set 1 for main to change 97648 status Accepted Under Review <span data-processor="relativetime" data-value="2026-11-14T13:58:56+00:00" > 11/14/26, 13:58 </span>