[MGNLUI-5660] CanMove rule should reuse the logic from DropConstraint Created: 10/Feb/20  Updated: 16/Mar/21  Resolved: 16/Mar/21

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

Type: Improvement Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Won't Do 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)

 Description   

Currently the CanMove rule implements its own logic separate from the of the DropConstraint. Since both classes deal with move actions we should try to reuse the latter from the former instead of duplicating the logic.

This should also solve the current problem with CanMove only receiving the first source item of a move action - even when multiple are selected.



 Comments   
Comment by Michael Duerig [ 16/Mar/21 ]

Resolving as requested by had and discussed with rkovarik

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