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

Default to jcrChildNodeProvider in JcrMultiFieldDefinition to simplify config and encourage good practice

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 6.2.4
    • None
    • None
    • None
    • Yes
    • Yes
    • UI FW 13
    • 1

      We want to

      • avoid currentItemProvider usage with composite/multis/switchables, b/c it leads to issues like MGNLUI-5886 and
      • simplify yaml definitions further.

      Thus we're adding default to JcrMultiFieldDefinition

      This does not pose risk to compatibility because formerly you had to specify the itemProvider. This only takes effect when itemProvider is not specified which before would result in exception.

      Also, modify the example in https://documentation.magnolia-cms.com/display/DOCS62/Multi+field for JCR Multi Field not to use currentItemProvider there. WIth this change, the whole itemProvider part can (and should) be removed. If we want to how something there still, use jcrChildNodeProvider instead to avoid suggesting CIP - bad practice.

        Acceptance criteria

              sdemocko Šimon Demočko
              sdemocko Šimon Demočko
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 29m
                    29m