[MGNLUI-4213] NodesAndPropsDropConstraint doesn't take into account folder node Created: 25/May/17  Updated: 11/Mar/21  Resolved: 11/Mar/21

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

Type: Improvement Priority: Neutral
Reporter: Oanh Thai Hoang Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File can-move-folder-inside-content-node.png     PNG File can-not-add-folder-inside-content-constraint.png    
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   

Below case you can reproduce in Site app as well as Configuration app.

  • Prepare 2 folder node and 2 content node as following image
  • Observe: Can't add folder inside content
  • Drag untitled0 folder inside untitled1 content node
  • Observe: folder can drag inside content node
  • Expectation: folder can't drag inside content node. Drag drop behaviour must consistent with availability configuration (/modules/ui-admincentral/apps/configuration/subApps/browser/actions/addFolder/availability that prevent adding folder inside content)

Source of problem: folder node in Config app is not really a real folder type. It is mgnl:content type


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