Page tree
Skip to end of metadata
Go to start of metadata

(plus) New suggested key

(thumbs down) Key suggested for deprecation

(tick) old key which is consistent and does't require changes

(question) To be discussed

Apps

(plus) "apps.<app>.label",

(thumbs down) "<app>.app.label"

App launcher group

(plus) "appLauncherLayout.groups.<group>.label", //you can immediately identify in an i18n file that it's a group name (compared to the old keys below), moreover appLauncherLayout is the name of the app launcher configuration node

(thumbs down) "app-launcher.<group>.label",
(thumbs down) "app-launcher.<group>"

Actionbar

Sections

 //new suggested keys respect the path in configuration:

(plus) "apps.<app>.subApps.<subapp>.actionbar.sections.<section>.label",

(plus) "subApps.<subapp>.actionbar.sections.<section>.label", 

(plus) "actionbar.sections.<section>.label", 

vs

(thumbs down) "<app>.<subapp>.actionbar.sections.<section>.label", 

(thumbs down) "<app>.<subapp>.actionbar.sections.<section>.label", 
(thumbs down) "<app>.<subapp>.actionbar.sections.<section>.label",
(thumbs down) "<app>.<subapp>.actionbar.sections.<section>.label",

Actions

New suggested keys:

(plus) "apps.<app>.subApps.browser.actions.<action>.label",
(plus) "subApps.browser.actions.<action>.label",

(tick) "actions.<action>.label",

Currently supported keys:

(question) "<app>.browser.actions.<action>.label", //short key, doesn't respect configuration path but is shorter

Columns

New suggested keys:

(question) "apps.<app>.subApps.<subapp>.workbench.contentViews.<view-name>.columns.<column-name>.label",
(question) "subApps.<subapp>.workbench.contentViews.<view-name>.columns.<column-name>.label",
(question) "workbench.contentViews.<view-name>.columns.<column-name>.label",

(tick) "columns.<column-name>.label",  //we could probably support this one, if no objections

vs currently supported keys:

(question) "<app>.<subapp>.views.<view-type>.<column-name>.label",

(question) "<app>.<subapp>.views.<view-type>.<column-name>.label",

(question) "<app>.<subapp>.views.<view-type>.<column-name>.label",

(question) "<app>.<subapp>.views.<view-type>.<column-name>.label",

(question) "<app>.<subapp>.views.<view-type>.<column-name>.label",

(question) "<app>.<subapp>.views.<view-type><column-name>.label",

Pretty hard to remember, isn't it? (big grin) Also notice <view-type>. This is tree/list and it doesn't matter how is the view called in config although all the other parts are always the node names in JCR (yaml). 

Forms

Dialog

New suggested keys:

(plus) "<module>.dialogs.<dialogPath>.label",
(plus) "dialogs.<dialogPath>.label", //this is "must have". We currently cannot use module-independent translations

(question) "dialogs.testDialog.label",

//currently supported keys:
(thumbs down) "<module>.<dialogPath>.label",

Tabs

New suggested keys:

(plus) "<module>.dialogs.<dialogPath>.form.tabs.<tab>.label",
(plus) "dialogs.<dialogPath>.form.tabs.<tab>.label",
(plus) "form.tabs.<tab>.label",

//currently supported keys:
(question) "<module>.<dialogPath>.<tab>.label", Do we still want to have this one? It's shorter but not a big difference and it doesn't respect configuration path.
(thumbs down) "<tab>.label", //That's pretty dangerous since it's too short and without a type prefix. How you can possibly know where it belongs by looking in the translation file? Is it for template/dialog/app?

Fields

New suggested keys:

(plus) "<module>.dialogs.<dialogPath>.form.tabs.<tab>.fields.<field>.label",
(question) "dialogs.<dialogPath>.form.tabs.<tab>.fields.<field>.label",
(question) "form.tabs.<tab>.fields.<field>.label",

(tick) "fields.<field>.label" //we might want to have generic translation for all fields with this name (fallback)

//currently supported keys:
(question) "<module>.<dialogPath>.<tab>.<field>.label", //vs "<module>.dialogs.<dialogPath>.form.tabs.<tab>.fields.<field>.label",

(question) "<module>.<dialogPath>.<tab>.<field>.label",

(question) "<module>.<dialog>.<tab>.<field>.label",

(question) "<module>.<dialog>.<tab>.<field>.label", //vs "form.tabs.<tab>.fields.<field>.label",

(question) "<module>.<dialog>.<tab>.<field>.label",

 

Validators

New suggested keys:

(tick) <parentFieldI18nKey>validators.<validator>.errorMessage //respects configuration path

//currently supported keys:

(thumbs down) <parentFieldI18nKey>validation.errorMessage //no information about validator, just field definition

 

 

  • No labels