Bug: Duplicating any action inside /lib subfolders always moves it to the root /lib/ directory
Summary
When duplicating any action file located in a subfolder under /lib, Wappler always places the duplicated file in the root /lib/ folder, ignoring the original directory structure.
This occurs regardless of how deep the original file is nested.
Steps to Reproduce
-
Open the Library panel.
-
Navigate to any action located in a subfolder under
/lib/, for example:/lib/shared/core/contracts/address/mount-object.json -
Right-click the file and choose Duplicate.
-
Observe the location of the newly created file.
Expected Behavior
The duplicated file should be created in the same folder as the original file:
/lib/shared/core/contracts/address/mount-object_copy.json
Actual Behavior
The duplicated file is always placed in the root /lib/ directory, losing its original folder hierarchy:
/lib/mount-object_copy.json
Environment
-
App: Wappler
-
Version: 7.4.1
-
OS: Windows 11 x64
-
Project Type: Node.js backend
-
Project Structure: Modular, reusable server actions located under
/lib/shared/...
Additional Information
-
The issue happens with any file duplicated inside any subfolder within
/lib. -
This includes both deeply nested and single-level subdirectories.
-
The bug does not occur in other project folders (e.g.,
/api,/modules, etc.). -
Manual correction is possible by moving the file afterward, but this breaks workflow and risks overwriting existing actions.
Attachments
-
Screenshot 2025-11-06 194413.png— Original action located in/lib/shared/core/contracts/address/mount-object/ -
Screenshot 2025-11-06 194433.png— Duplicated action incorrectly appearing in/lib/
