[FrameworkBundle] call method with Translator component only

[xabbuh]

Q	A
Branch?	4.2
Bug fix?	yes
New feature?	no
BC breaks?	no
Deprecations?	no
Tests pass?	yes
Fixed tickets	#31152
License	MIT
Doc PR

[notrix]

👍

[nicolas-grekas]

Thank you @xabbuh.

[jsamouh]

Class string instead of ::class won’t be better ?

[stof]

@jsamouh no. The ::class allows us to rely on use statements (and also helps IDEs find it as a usage of the class), and it is still fine even when the class does not exists, as this ::class constant is a special one in PHP. It is entirely resolved by the compiler and does not require the class to exist.
For any code written in symfony 3.4+, we can use it (as that was introduced in PHP 5.5).

[jsamouh]

thanks for the explanation

[d42ohpaz]

Another solution that would not require installing anything temporarily is to tell composer to avoid using 4.2.6 of the symfony/framework bundle:

"symfony/framework-bundle": "^4.2,!=4.2.7",

This will force composer to downgrade/skip 4.2.7 and not produce any missing interface errors.

[nCrazed]

Is there an ETA for this to be released?

Considering that some of the recently discovered security problems (e.g. CVE-2019-10909) apply to all 4.2.* version prior to 4.2.7 effectively blocking the 4.1 to 4.2 upgrade.

[snebes]

@nCrazed The normal release schedule is every 2 weeks, which would be May 28. Assuming they don't release early.

The work around from @Gemorroj was to:

temporary add to requirements "symfony/translation": "4.2.*", to fix this

[vincentchalamon]

What about using the symfony/validator component out of a Symfony project (without the FrameworkBundle)? As the Symfony\Component\Validator\Util\LegacyTranslatorProxy implements an interface probably not installed (Symfony\Component\Translation\TranslatorInterface), it may not work, right? Cause the symfony/validator component doesn't require the symfony/translator

[xabbuh]

@vincentchalamon But in that case you do not have the need to use the LegacyTranslatorProxy class at all.