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

DOC: currentItemProvider should not be used in multi fields

    XMLWordPrintable

Details

    Description

      We want to avoid currentItemProvider usage with multis (may look for other candidates from code perspective in ConfiguredComplexPropertyDefinition), b/c it leads to issues like MGNLUI-5886.

      The multi nodes could then be resolved by multiple fields that are using currentItemProvider, if they would resolve the same nodes - effectively overwriting each other's contents. Another problem that would result from using currentItemProvider is that if the multi field would be set to resolve non-strictly (strict property set to false, which is the default), the multi would be resolving irrelevant nodes (everything in the parent) which would result in errors.

      One such place where this could be noted is in 
      https://documentation.magnolia-cms.com/display/DOCS62/Field+definition#Fielddefinition-Commonfieldproperties. Also present here https://documentation.magnolia-cms.com/display/DOCS62/Item+providers though some clarification is already next to it, to it might be better to make it clearer.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR