Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-7720

JCR Yaml Import is not taking account of null properties

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: 6.1.4
    • Fix Version/s: 5.7.7, 6.1.6, 6.2.1
    • Component/s: None
    • Labels:
    • Epic Link:
    • Sprint:
      Maintenance 1, Maintenance 2
    • Story Points:
      3
    • Magnolia Release:
      5.7.7, 6.1.6, 6.2.1

      Description

      The method yaml2Jcr from DataTransporter class it's not taking on account properties with null values.

      Stepts to reproduce:

      Create the following structure at, e.g, config workspace:

      'parent':
      'property1':
      'property2': value

      Export as Yaml and delete the parent node. Now, if the config.parent.yaml file is imported, the property property1 is a contentNode instead of an attribute.

      Regards

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jalonso Jesus Alonso
                Reporter:
                ccantalapiedra Carlos Cantalapiedra
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                  Time Tracking

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