single , multiple or checkbox translation access

[ycamus]

| Bug? | no
| New Feature? | yes
| Sulu Version | 1.2.0-RC4

Actual Behavior

when using content type single , multiple or checkbox in page definition, you define values and meta
(translation).
When it come to ui, view, only Value is returned, instead of both value and translation.

Expected Behavior

Get the translation and value in View/ui

Steps to Reproduce

use the page type : Exemple
single should output "option 1" (translation) it does output "option1"

Possible Solutions

Switch the return value to array.

[danrot]

Sadly it is not as easy as described here... People might also want to use the checkboxes as a kind of setting, and just check in the twig template if the selection contains some value. You could think of a group of checkboxes defining if the template should display specific parts.

I'd say we pass the meta stuff via the view variable. Maybe we could also only pass the current localization (including fallbacks in case the exact language does not exist).

Or maybe we could even introduce another meta variable? Because the view variable is actually holding whatever has been selected by the content manager, and the meta stuff is coming from a configuration file.

[ycamus]

my pov would say the hard part is getting the data without breaking the current state.

If you change content.single = value to content.single.value=value, that would break the current users twig on update
Unless you go for something like __toString (){ return value) and keep the 2 data?

But if you go for view.single.... i wouldn't mind either, will just need a bit of doc about it, so ppl dont get lost.

[danrot]

There is already a view variable, where it would suit better IMO, since, as I described, it is more configuration like content. But however, that would also be a BC break 😕