i18n keys: As a developer I don’t have to define i18n keys for every translatable item, if they follow the convention, so that the process is less redundant and error prone
(MGNLUI-1826)
|
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Sprint: | 5.1 Beta1- Frontend, 5.1 - Final |
| Description |
|
Currently ActionDefinitionKeyGenerator expects the root for ActionDefinition in the i18nAble hierarchy of objects to be an instance of AppDescriptor. This should be the most common case in content apps, however, since actions are configured in many places, we need to handle the case where the root is other than Appdescriptor, e.g. MessageViewDefinition, DialogDefinition, MediaEditorDefinition, etc. |