Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-3354

Generate i18n keys not referencing module name or id for forms and actions

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.3.8
    • Component/s: actionbar, forms, pages app
    • Labels:
      None
    • Magnolia Release:
      5.3.8

      Description

      This should allow us to use generic keys for generic actions and labels, such as workflow ones, instead of being forced to create i18n messages.properties for each module requiring them.
      E.g. pages app defines pages.publish.message.content.repository=Workspace whereas it could simply be publish.message.content.repository=Workspace (of course, such keys should be moved to a more "generic" module than pages) and be reused by other modules. See also linked issue.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              fgrilli Federico Grilli
              Reporter:
              fgrilli Federico Grilli
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: