[Bug]: Duplicates the folder structure instead of moving its contents #992

Describe the bug

Renaming a nested folder duplicates the folder structure instead of moving its contents

To reproduce

massCode version: 6.2.1
Operating system: Windows 11

Steps to reproduce:

Create the following folder structure:
Folder A / Folder B / Folder C

Add content inside Folder C.

Rename Folder B to Folder B1 from the massCode sidebar.

Expected result:

Folder A / Folder B1 / Folder C exists and contains the original data. Folder B no longer exists.

Actual result:

Two separate structures are shown:

Folder A / Folder B / Folder C — the original folder remains and still contains all data.

Folder A / Folder B1 / Folder C — a new but empty folder structure is created.

The issue occurs with both synchronized and non-synchronized vault locations on Windows 11. Renaming a folder without nested subfolders works normally.

App Version and Architecture

massCode version: 6.2.1

System info

Windows 11

Validations

• Follow our Code of Conduct
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.