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

I18n: I can reuse the keys between modules

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 5.4.6
    • None
    • dialogs
    • None
    • Yes
    • Kromeriz 35
    • 3

      We decided to implement only minimal changes: https://wiki.magnolia-cms.com/display/DEV/Minimal+required+changes

      We currently generate these keys for templates:
      templates.components.componentName.title
      moduleName:templates.components.componentName.title
      But that's not the case for dialogs:
      moduleName:components.componentName.label
      It should be consistent with templates (also to force more 'logical' keys)

      Open Questions:
      There is disagreement on what the consistant keys should be.

      • Should the keys reflect the full "definition path", therefore being predictable - yet verbose?
      • Should some keys support skipping parts of the definition - ie specify an app and a field, but not a subapp or view?

      Next:
      A list of all current keys will be created, which stakeholders from PD & PM can evaluate. Then another meeting to hopefully nail down the key generators we want to support, what patterns they should follow, and which ones we may want to deprecate.
      https://jira.magnolia-cms.com/browse/DEV-137

        Acceptance criteria

              rkovarik Roman Kovařík
              rkovarik Roman Kovařík
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0d
                    0d
                    Logged:
                    Time Spent - 1d 5.5h
                    1d 5.5h