[MAGNOLIA-5140] NodeUtil.renameNode implementation should keep the position of the node being renamed Created: 27/Jun/13  Updated: 12/Aug/13  Resolved: 27/Jun/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.5, 5.0
Fix Version/s: 4.5.10, 5.0.1

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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
Date of First Response:

 Description   

Currently it only uses session.move(newNode, oldName) which automatically place newNode as the last node among its siblings.



 Comments   
Comment by Tobias Mattsson [ 27/Jun/13 ]

Couldn't we use getSiblingAfter(Node) to make the code a bit more elegant ?

Generated at Mon Feb 12 04:02:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.