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

Remove spurious multiple subwidget ids computation

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 7.1
    • Fix Version/s: 7.2
    • Component/s: Layouts & Widgets
    • Tags:
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      Ids are generated on the fly only when needed, making ids usually more simple.

      Computation is now only done once inside nxl:layoutRowWidget and nxl:subWidget tags iterations, unless attribute recomputeIds="true" is added explicitely to the tag.

      Show
      Ids are generated on the fly only when needed, making ids usually more simple. Computation is now only done once inside nxl:layoutRowWidget and nxl:subWidget tags iterations, unless attribute recomputeIds="true" is added explicitely to the tag.
    • Sprint:
      nxNag Sprint 7.1-5

      Description

      Sometimes subwidget ids are generated several times, leading to multiple nxw_widget_1, nxw_widget_2 even if it's not always necessary.

      The widget is must be filed only when the widget variable is made available to the context, and subwidgets usually do not need their ids to be filled at this point: the nxl:subWidget tag should be the one performing the iteration, so it can ensure that widget ids are generated then.

      Same for bound value name (than can change after first computation, when applying subwidgets to model.rowData inside lists, for instance)

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.