@TikWind We need a proposal to make our i18n cleaner and reasonable.
Hi, I have a proposal the key can be like this : [basicModule].[moduleName].[elementName].[...desc]
basic keys (the first tow levels) divide according to the directory structure:
eg: app.pwa, page.consumer, component.actionBar
sub keys divide according to element +description
eg: app.pwa.message.offline, component.actionBar.button.nextStep
If the the text is the part of a element, we can use [elementName.props]
eg: page.consumer.proTable.columns.username
common texts, we should not repeat in other part, we can divide them to component.global.xxx
eg: component.global.button.okText, component.global.status.loading and so on
Agree +1
Most helpful comment
Hi, I have a proposal the key can be like this : [basicModule].[moduleName].[elementName].[...desc]
basic keys (the first tow levels) divide according to the directory structure:
eg: app.pwa, page.consumer, component.actionBar
sub keys divide according to element +description
eg: app.pwa.message.offline, component.actionBar.button.nextStep
If the the text is the part of a element, we can use [elementName.props]
eg: page.consumer.proTable.columns.username
common texts, we should not repeat in other part, we can divide them to component.global.xxx
eg: component.global.button.okText, component.global.status.loading and so on