Problem/Motivation

Props in XB have no (translatable) labels.

Need these to be human readable and translatable.

Related to #3493070: SDC `enum` props should have translatable labels: use `meta:enum`

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

griffynh created an issue. See original summary.

griffynh’s picture

Issue summary: View changes
wim leers’s picture

wim leers’s picture

Priority: Normal » Major
wim leers’s picture

Assigned: Unassigned » pdureau

Does UI Patterns have a solution for this, similar to #3493070-4: SDC `enum` props should have translatable labels: use `meta:enum`? 🤞

penyaskito’s picture

Now that #3390712: Add component variants to SDC landed, we will have the same problem there.

Whatever we end up doing here, should be done for variants.

It might not be strictly consistent with e.g. meta:enums, but IMHO they are different enough usecases to justify that.

wim leers’s picture

phenaproxima’s picture

I wonder if this could dovetail with the work being done to make config actions translatable? The current approach proposes adding a !translate YAML tag, which presumably would allow potx to find the strings that need to be translated for a project (which would include recipes and, potentially, themes that expose SDCs).

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

svendecabooter’s picture

It would be good if we could use the same logic for translating recipe input / config actions, and apply it to SDCs.
So that would make this issue postponed on the recipe one, which seems to need quite some work still..

Are the same outstanding issues for recipes also applicable here (monolingual non-English / multilingual non-English)? Or not, because the SDCs are not config objects?