[MGNLPN-130] Migrate trait rule aggregator field to use the new delegating transformers. Created: 28/May/14  Updated: 11/Jun/14  Resolved: 30/May/14

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Task Priority: Major
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLPN-162 mgnl:ruleSet node is not removed even... Closed
dependency
depends upon MGNLUI-2871 Enhance the behavior of complex fields Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Personalisation

 Description   

We would benefit from using the newly introduced delegating value transformers:

  • The complexity of the trait fields would be unlimited as no assumptions will be made about the sub-fields.
  • The implementation of the transformer would be simplified because it would not have to take care of sub-field JCR I/O operations.

The only known drawback of the approach is that the aggregating transformer wouldn't be able to control the property names of the sub-nodes (handled with sub-fields/transformers). Then the sub-transformers should take care of correct naming and prefixes. For the simple case (one-property fields) we introduce the transformer which enforces 'value' as a property name.


Generated at Mon Feb 12 06:34:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.