Fix for issue #7242 : broken translations for enums in forms

[FoxCie]

With symfony/form >= v7.3.5, EnumType uses the keys of the choices option as labels for the enum cases, breaking the translation that happened previously when enum implements TranslatableInterface. The translation now occurs only when the choices option has integer keys (more precisely, currently only if it satisfies array_list()). Fixing this by changing the way ChoiceFields are configured with the ChoiceConfigurator, to define the choices option with integer keys when the enum is translatable.

[Seb33300]

This sounds like a bug in Symfony?

[FoxCie]

They acknowledged that the previous behaviour was actually the bug. When dealing with choices, the keys of the array should be the labels. It is not explicit on EnumType, but on its parent ChoiceType, the doc states that clearly :

Source : https://symfony.com/doc/current/reference/forms/types/choice.html#choices .

The thing is that it was actually impossible to change an enum's labels with the choices array with the previous behaviour. Now it is possible, but the old behaviour is still present if the keys are integers (e.g. when giving the ::cases() as the choices).

EDIT : the associated bug in Symfony is here : symfony/symfony#61927 .

[Seb33300]

This still looks wrong to me. The EnumType should transform the data to make it compatible with ChoiceType

[FoxCie]

It is what is done. It is just the label that can be changed by passing a string value as the key of the array. EnumType does what should be done so that the values are properly handled and converted. If you think this is not appropriate, you could open an issue on the Symfony side.

[siggidiel]

Hey guys. What's the status of this? The translations of enum based ChoiceFields on form pages are broken for a while already. Any updates on this? :)

[rdevaissiere]

Thanks for the PR @FoxCie. It works well for me in forms but there's an issue with the selected value(s) as they come up empty in index/detail pages. I can't quite figure out a fix for now but choiceMessages is not populated in ChoiceConfigurator::configure(). Hope this is helpful.

[FoxCie]

Thanks for the PR @FoxCie. It works well for me in forms but there's an issue with the selected value(s) as they come up empty in index/detail pages. I can't quite figure out a fix for now but choiceMessages is not populated in ChoiceConfigurator::configure(). Hope this is helpful.

Nice catch, we should only change forms, not the other pages. I just pushed a version that should fix that (by just checking if the page is index or details, but I am not sure if this is the correct thing to do, there maybe a better way by changing more what was done before).