Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug: moveNode doesn’t keep node order #16

Closed
sabberworm opened this issue Oct 17, 2024 · 0 comments · Fixed by #23
Closed

Bug: moveNode doesn’t keep node order #16

sabberworm opened this issue Oct 17, 2024 · 0 comments · Fixed by #23
Labels
bug Something isn't working

Comments

@sabberworm
Copy link
Collaborator

When moveNode is used to rename a node within the same (orderable) parent, it is moved to become the last sibling.
We should try to keep the node at the same position in this specific case.
@sabberworm sabberworm added the bug Something isn't working label Oct 17, 2024
sabberworm added a commit that referenced this issue Oct 30, 2024
@sabberworm
fix(runner): renamed nodes now keep their position
816ad26 
closes #16
sabberworm added a commit that referenced this issue Oct 30, 2024
@sabberworm
fix(runner): renamed nodes now keep their position
26b763d 
closes #16
@sabberworm sabberworm mentioned this issue Oct 31, 2024
Merged
sabberworm added a commit that referenced this issue Oct 31, 2024
@sabberworm
fix(runner): renamed nodes now keep their position
a944fb7 
closes #16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bugfix/various swisscom/JCR-Hopper
1 participant
@sabberworm