[MGNLPN-162] mgnl:ruleSet node is not removed even if all the traits have been removed. Created: 11/Jun/14  Updated: 11/Jun/14  Resolved: 11/Jun/14

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: 1.0
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

Issue Links:
causality
caused by MGNLPN-130 Migrate trait rule aggregator field t... Closed
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   

This issue once fixed (MGNLPN-101) re-occurred during the re-factoring of the transformers and introduction of the delegating transformers.



 Comments   
Comment by Aleksandr Pchelintcev [ 11/Jun/14 ]

Changed the way the presence of traits to be written to the JCR is determined - now we look into the actual PropertySetItem that fields work with. Improved the test so it works not with the case of an initially empty rule-set (which would pass anyway), but with one that has an existing trait (commit hash is 6829b4b).

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