[MGNLUI-2717] With drag-and-drop before and after a node you can create same name siblings Created: 28/Feb/14  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: content app
Affects Version/s: 5.2.2
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Frank Sommer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File screenshot-1.jpg    
Issue Links:
duplicate
is duplicated by MAGNOLIA-7005 It's possible to create same name sib... 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
Visible to:
Rainer Blumenthal

 Description   

In MGNLUI-1292 you fix the same name siblings for dropping a node in to another. But the fix does not cover the dropping before and after a node. You should add the node name check in BaseDropConstraint for the other cases.

Furthermore it seems only to work on root level (see screenshot-1). Reason is the root node is not restricted to have same name siblings. There seems to be a setting for repository setup. See Repository.NODE_TYPE_MANAGEMENT_SAME_NAME_SIBLINGS_SUPPORTED


Generated at Mon Feb 12 08:59:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.