Translations: incorrect domain using "t" function and named domain argument

[noofaq]

Symfony version(s) affected

5.4.2

Description

Using Symfony\Component\Translation\t function and using named domain argument "translation:extract" and "debug:translations" use incorrect domain (default one messages is used).

How to reproduce

class DAMFileNameTemplate extends Constraint
{
    public function getMessage()
    {
        return t('error.dam_file_name_template_evaluation', domain: 'validators');
    }
}

Calling debug:translation reports incorrect domain:

Workaround:

class DAMFileNameTemplate extends Constraint
{
    public function getMessage()
    {
        return t('error.dam_file_name_template_evaluation', [], 'validators');
    }
}

Calling debug:translation reports correctly:

Possible Solution

No response

Additional Context

No response

[fancyweb]

Not a bug for me but probably an unimplemented case in the Translation PhpExtractor. Could you have a look?

[welcoMattic]

We discussed with @stof & @nicolas-grekas about adding support of named arguments in PhpExtractor. It seems to require to add a new optional dependency on https://github.com/nikic/PHP-Parser to leverage AST features and avoid to continue with tokens, especially since we will probably have to add support of some other syntax (like inline variable assignation, see #42285).