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

JcrDatasourceDefinition#nodeNameProperty should default to null

    XMLWordPrintable

Details

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

    Description

      Steps to reproduce

      Rename a page using rename item (not editing via detail). You can use special characters.

      Expected results

      Node is renamed, no jcrName property.

      Actual results

      JcrName property is created.

      Workaround

      You can still rename the item, just the content of the field might be confusing.

      Development notes

      Presense of property <field name> now always takes precedence when loading property but should respect if nodeNameProperty of JcrDatasource is null (= use just real node name) instead.

      As the default for nodeNameProperty is jcrName and you can't set it to null via config without getting warning in def. app, should we use null as default?

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                rkovarik Roman Kovařík
                sdemocko Šimon Demočko
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD