[MAGNOLIA-7720] JCR Yaml Import is not taking account of null properties Created: 12/Feb/20  Updated: 26/Oct/20  Resolved: 08/Apr/20

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 6.1.4
Fix Version/s: 5.7.7, 6.1.6, 6.2.1

Type: Bug Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Jesus Alonso
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: 0.25d
Time Spent: 0.95h
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by MAGNOLIA-7652 OOME when exporting to YAML Closed
causality
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Support
Sprint: Maintenance 1, Maintenance 2
Story Points: 3

 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



 Comments   
Comment by Jesus Alonso [ 08/Apr/20 ]

Fixed some issues with text properties that can produce broken exports. In particular:

  • Export empty strings
  • Export numerical strings
  • Export NAME nodes always with single quotes

Backported to release/6.1

Generated at Mon Feb 12 04:26:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.