Follow-up to #1763974: Convert entity type info into plugins
Blocked by #1827424: Parse annotations recursively

Currently, nested values in annotations cannot be translated. Once they are, we need to go back and wrap the labels of the bundles and view modes in @Translation().

Comments

jibran’s picture

jibran
he/him
Primary language Urdu
Location Toronto, Canada
commented
Status: Postponed » Active

#1827424: Parse annotations recursively is fixed.

amateescu’s picture

amateescu commented
Status: Active » Closed (works as designed)

Bundles and view modes have their own info hooks now and can be translated just fine with t().

andypost’s picture

andypost
he/him
Primary language Russian
commented
Status: Closed (works as designed) » Active
Issue tags: +D8MI

Neither hook_entity_view_mode_info() nor bundle() before #1735118: Convert Field API to CMI have enough context to be translatable

amateescu’s picture

amateescu commented

I have no idea what you're trying to say. What context?

andypost’s picture

andypost
he/him
Primary language Russian
commented

I mean translation context. Bundles would be config entities that have config translation.
But view modes as they defined within hook looks like content context of translation

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Issue summary: View changes
Status: Active » Closed (cannot reproduce)

It's up to the implementation to make bundle translatable, and as most are now config based, they implicitly rely on config translation. Same for view modes, which are now config.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Closed (cannot reproduce) » Closed (works as designed)

Ups.