[MGNLUI-6812] Allow define DropConstraint for CanMoveRule Created: 10/Aug/21  Updated: 26/Aug/21  Resolved: 12/Aug/21

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

Type: Improvement Priority: Neutral
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by PAGES-444 User that is disalowed to create page... Closed
documentation
to be documented by MGNLUI-6819 DOC: 'CanMoveRuleDefinition' uses 'dr... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: UI framework implementation
Sprint: UI FW 34
Story Points: 0

 Description   

CanMoveRule only checks if item isn't moved to inside himself, but we need to define dropConstrain for more complex checks.
In Magnolia 5 framework dropConstraint was defined on workbench level and it was used by views and actions, but in Magnolia 6 framework this is defined on view level. That means action/rules doesn't have access to it an we need to define dropConstrain directly in CanMoveRule.

AC:

  • Allow specify dropConstrain in CanMoveRuleDefinition

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