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

Make ds definititon resolution algorithm treat WithDatasource iterface the same way as if the definition was there in the storage

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Neutral
    • 6.2
    • None
    • None
    • None

    Description

      The problem was uncovered by the tasks app: the DS definition defined on the app level (via app descriptor) was queried indirectly and got cached in session storage (because that's how our scopes work).

      As a result as per current DS def resolution mechanism - that cached definition was taking precedence over the DS defs configured in sub-app descriptors due to technical detail: the "free-roaming" DS definition stream was concatenated by the ones provided by other definitions and the first one was to be picked.

      The lined changeset shifts the choice preference to the Ui context proximity: if there's a descriptor that has DS configured closer to the current view than the explicitly cached DS def somewhere far (e.g. in the app scope), prefer the closer one.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              apchelintcev Aleksandr Pchelintcev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR