[MGNLUI-5687] Hardening conversions of old definitions to new framework Created: 28/Feb/20  Updated: 04/May/20  Resolved: 13/Mar/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2

Type: Improvement Priority: Neutral
Reporter: Šimon Demočko Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.75d
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MGNLUI-5848 Adapt TwinColSelectFieldConverter to ... Closed
Relates
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)
Documentation update required:
Yes
Date of First Response:
Sprint: UI Framework 18, UI Framework 19
Story Points: 8

 Description   

Within this ticket a lot of ad-hoc found issues with conversions were fixed. Mostly what was found within DEV-1413.

Original old description

EDIT: converted field is working properly, only this label is broken via converter. In fact converter should handle these cases by disabling field unless default SwitchableTransformer or CookieFieldTransformer are used.

 

In the attached image the label informs us about non-converted field.

Can be found in a Choose Audience dialog triggered on a page variant in the new pages app.



 Comments   
Comment by Adam Siska [ 13/Mar/20 ]

DOCU: changing behaviour of DefinitionConverter to fallback to "empty" field for unsupported configuration of field (so far it fallbacks only if converter for the field definition wasn't available at all).

Comment by Ashraf Khamis [ 02/Apr/20 ]

https://documentation.magnolia-cms.com/display/DOCS62/Field+converters updated on March 16th. Reviewed by Adam.

Generated at Mon Feb 12 09:29:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.