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

Release ItemProviderStrategy implementations from the dependency on the parent item provider strategy

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Done
    • Neutral
    • 6.2
    • None
    • None
    • None

    Description

      The bug was uncovered when the complex fields were tested in dialogs: unlike the detail sub-apps where the root item provider strategy is always there, the dialogs don't set one.

      The complext fields' item prov impls, however, try to inject the parent one and when it is not present - fail. The reason for such injection attempt is that the child editors need to access the parent item/node to resolve the sub-item to bind themselves to.

      However, instead of injecting the strategy we could change its root API and pass the parent item directly, should it exist!

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Time Spent - 0.7h Remaining Estimate - 0.25d
                    0.25d
                    Logged:
                    Time Spent - 0.7h Remaining Estimate - 0.25d
                    0.7h