[MGNLDEMO-219] Lists (dropdown, radio buttons) truncated since switching to YAML Created: 28/Jun/17  Updated: 23/Aug/17  Resolved: 28/Jun/17

Status: Closed
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: 1.1.4
Fix Version/s: 1.1.4

Type: Bug Priority: Blocker
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: regression
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File options.png     PNG File requirements.png    
Issue Links:
causality
caused by MGNLDEMO-214 Demonstrate YAML bootstrap format Closed
relation
is related to MAGNOLIA-7078 YAML exporter should respect YAML syn... Accepted
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: LD: Fundamental features
Sprint: Basel 102
Story Points: 2

 Description   

Booking a tour is no longer functioning correctly since the switch to YAML, cf. screenshots compared to the snippets below.

The problem is that the second and subsequent elements of lists aren't indented, and therefore not recognized as valid YAML.

                  'labels_de': 'Gluten Frei:gluten-free
Halal:halal
Kosher:kosher
Vegan:vegan
Vegetarier:vegeterian
Keine spezielle Bedürfnisse:none'
                  'labels': 'Gluten Free:gluten-free
Halal:halal
Kosher:kosher
Vegan:vegan
Vegetarian:vegeterian
No Special Requirements:none'
                'labels_de': 'Ja:yes
Nein:no'
                'labels': 'Yes:yes
No:no'


 Comments   
Comment by Federico Grilli [ 28/Jun/17 ]

Regression found out during pre-release QA. Consensus also from PM was to fix it both because it should be a quick win and, even though a minor glitch, it would give a bad impression to evaluators. Hence the blocker priority.

Comment by Maxime Michel [ 28/Jun/17 ]

The problem turned out to be that whether the current syntax or the YAML multi-line > is used, the elements of the lists are joined on a single line, which prevents the form module from actually creating a list. For instance:

Yes:yes No:no

Going with the YAML | syntax means that a \n will be added after each list element, like this: Yes:yes\nNo:no. This behavior solved the problem, and is how it must have been behaving with XML all along.

Generated at Mon Feb 12 05:17:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.