[MGNLPN-316] Move resolving of variants for editor to a dedicated component Created: 15/Aug/16  Updated: 22/Aug/16  Resolved: 18/Aug/16

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

Type: Story Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
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)
Date of First Response:
Epic Link: Component P13N
Sprint: Kromeriz 57
Story Points: 2

 Description   

The variant which is selected by the editor is resolved in lots of actions thus in the node wrapper.
Move the logic to a dedicated component so variants are resolved in a central place.



 Comments   
Comment by Evzen Fochr [ 16/Aug/16 ]

Failed tests:
IsNoVariantRuleTest.testIsNotAvailable:68
Expected: is <false>
but: was <true>
IsVariantRuleTest.testIsAvailable:55
Expected: is <true>
but: was <false>

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