Community
Participate
Working Groups
- Create a project P1 and set its location to be d:\test - Create a file in P1 - From the file system, create a folder f1 in d:\test - Select move from the project P1 - Type in d:\test\f1 and press OK Notice the move takes place. However, notice the directory d:\test is then deleted causing the sub dir f1 to be deleted too, and the file. NOTES:
PRODUCT VERSION: 0.131
Ooops... Moving the project to a subdir should be a valid operation. But the current behaviour seems... humm... "less than optimal" (being polite).
Project.checkDescription calls Workspace.validateProjectLocation which checks the location of the given description against the location of all the projects in the workspace to ensure that there is no overlapping. Unfortuanatly we skip over the current project because in most cases we don't want to consider the location of the current project as part of the validation. But this is one case were we do.
As a user that has just lost a considerable amount of code due to this bug, I would like to ask that its priority and severity be increased. After all, it's not like this bug is simply a feature that doesn't work--it actually deletes code(!!!)
Fixed. validateProjectLocation now disallows moving a project to a subdirectory of itself.
