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

Streamline ValueContext provisioning in choose dialogs

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Neutral
    • 6.2
    • None
    • None
    • None
    • UI Framework 16
    • 5

    Description

      Choose dialog typically manage the value context on their own and => are supposed to bind it themselves. However, due to a wrong component provider used to construct the action bindings of the chooser the latter get an outer UI context's value context injected.

      As a current workaround chooser interface exposes the getValueContext API, which can explicitly provide a value context to be used in actions, but that API is out of place, in-essential and needs to be removed, the context provisioning should be streamlined (be means of using the same component provider for both the view and the actions fired against that view).

      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