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.

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

Add confirmation for folders and files movement in File Tree #21778

Closed
Arilas opened this issue Mar 2, 2017 · 5 comments
Closed

Add confirmation for folders and files movement in File Tree #21778

Arilas opened this issue Mar 2, 2017 · 5 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@Arilas
Copy link

Arilas commented Mar 2, 2017

Some of developers accidentally move folders or files in another folder when inaccurate trying to open some file or expand folder (by moving mouse when doing action).
And sometimes he can just revert it using git or trying to find it manually.

It will be good to add optional prompt for confirmation for this actions. In future some of extensions can subscribe to this actions to perform refactoring (by changing paths in dependent components).

@isidorn
Copy link
Contributor

isidorn commented Mar 2, 2017

How did you get 8 thumbs up in 20 minutes? Is this an orchestrated effort :)

@bpasero
Copy link
Member

bpasero commented Mar 2, 2017

#1414

@bpasero bpasero closed this as completed Mar 2, 2017
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 2, 2017
@Arilas
Copy link
Author

Arilas commented Mar 2, 2017

@isidorn Just mentioned this issue is two of working chats 😃 . We all use VSCode for a while and sometimes had a problems with this.

@johnfrades
Copy link

is there any solution on this?

@bpasero
Copy link
Member

bpasero commented May 11, 2017

You can disable DND in the explorer via "explorer.enableDragAndDrop": false, but a confirmation dialog has not been added yet. I can look into that.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants