Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-15428

Allow defining aliases for layouts and widgets definitions

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.9.6-SNAPSHOT
    • Fix Version/s: 6.0
    • Component/s: Layouts & Widgets
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      Widgets and layouts configurations now accept aliases definitions, the returned definition has its original name (not the alias one).

      Examples:

      <widget name="myWidget" type="test">
        <aliases>
          <alias>oldWidgetName</alias>
          <alias>veryOldWidgetName</alias>
        </aliases>
      </widget>
      [...]
      <layout name="myLayout">
        <aliases>
          <alias>oldLayoutName</alias>
          <alias>veryOldLayoutName</alias>
        </aliases>
      </layout>
      
      Show
      Widgets and layouts configurations now accept aliases definitions, the returned definition has its original name (not the alias one). Examples: <widget name= "myWidget" type= "test" > <aliases> <alias>oldWidgetName</alias> <alias>veryOldWidgetName</alias> </aliases> </widget> [...] <layout name= "myLayout" > <aliases> <alias>oldLayoutName</alias> <alias>veryOldLayoutName</alias> </aliases> </layout>

      Description

      When migrating widgets and layouts definitions, it would be handy to be able to define aliases for deprecated definitions (so that they can point to a newer definition with a better name)

      For now this is useful for:

      • document_listing_ajax -> table_listing
      • search_listing_ajax -> table_listing

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: