[MGNLUI-5333] DOC: Valid Transformer implementations ported to ItemProviderStrategy Created: 20/Aug/19  Updated: 04/Mar/20  Resolved: 04/Mar/20

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

Type: Task Priority: Neutral
Reporter: Ashraf Khamis Assignee: Martin Drápela
Resolution: Fixed Votes: 0
Labels: fields, new-UI-framework, new-form, transformer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MGNLUI-5698 DOC: propertyNameDecorator property Closed
Relates
documentation
documents MGNLPN-444 Migrate personalization UI to new UI ... Closed
documents MGNLUI-5340 Implement special multi-value field b... Closed
relation
is related to MGNLUI-5383 DOC: Transforming field values - 6 UI Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: DOC: Documentation for Magnolia 6.2
Sprint: UI Framework 17, UI Framework 18
Story Points: 1

 Description   

ItemProviderStrategy is a simpler abstraction that has come to replace the Transformer functionality. While Transformer is responsible for both the read and write operations, ItemProviderStrategy only needs to know how to access the data with persistence typically handled elsewhere. This supposedly will simplify the port.

Results

Some existing Transformer implementations will be completely ditched, while those that are still valid will be ported to ItemProviderStrategy.

For the preliminary investigation, see DEV-1302. For the actual implementation, see MGNLUI-5340 and MGNLPN-444.

Note

The following 4 field Transformer classes are not listed at https://documentation.magnolia-cms.com/display/DOCS61/_Transformer+classes:

  • info.magnolia.ui.form.field.transformer.basic.BCryptTransformer
  • info.magnolia.ui.form.field.transformer.basic.ListToSetTransformer
  • info.magnolia.ui.form.field.transformer.basic.NotNullInitialStringValueTransformer
  • info.magnolia.ui.form.field.transformer.item.FileTransformer

Rico: I think those can be ditched, but let's wait for the implementation.


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