[MGNLPN-95] Make TraitAggregatorTransformer act correctly for both cases of mgnl:segment and mgnl:constraintSet. Created: 06/May/14  Updated: 07/May/14  Resolved: 06/May/14

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

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

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
Epic Link: Personalisation

 Description   

When editing trait set with a TraitAggregatorField for a segment we write all the auxiliary properties (operation, class) directly to the form node which is also an mgnl:segment node, this is correct.

When dealing with mgnl:constraintSet - the form node is the variant node, instead of writing directly to it we should write the data one level deeper (mgnl:constraintSet node).


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