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: | favorites |
| Affects Version/s: | 5.1 |
| Fix Version/s: | 5.1 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Christoph Meier |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Sprint: | 5.1 Beta1- Frontend, 5.1 - Final | ||||||||||||||||
| Comments |
| Comment by Christoph Meier [ 04/Sep/13 ] |
|
changed in info.magnolia.i18n
|
| Comment by Christoph Meier [ 04/Sep/13 ] |
|
fixed and pushed |
| Comment by Magnolia International [ 04/Sep/13 ] |
|
We need a better solution for unmodeled/unconfigured texts. See MAGNOLIA-5296 |