Move/copy picker: Possible to accidentally choose same folder, receive error

[jancborchardt]

Currently when moving/copying a file via the file picker, you can accidentally choose the same folder you are just moving as a target. In that case you just get an error "Could not move folder".

Instead, the current folder that you are moving should be grayed out to make clear that it’s the current folder being moved.

What do you think @nextcloud/designers

[nextcloud-bot]

GitMate.io thinks possibly related issues are #2851 (Moving shared folders), #4149 (Moveing file/folder selection), #3369 (Sharing of folders are not possible), #7629 (Create Folders when moving files), and #5448 (Error moving / renaming folders NC 12.0.0 (stable)).

[pixelipo]

Since we have both "Move" and "Copy" buttons, your approach makes most sense. Otherwise, Move action would default to Copy in case destination folder == source folder

[MorrisJobke]

Should maybe combined with #9931 (copy to same folder should create a duplicate file) and remove/gray out the "Move" button as @pixelipo explained it.

[szaimen]

At least copying into the same folder works now as far as I can see on c.nc.c. (it creates a new file which is named the same + (copy))
Please reopen or create a new issue if you still want to implement this for moving.