[#RSRP-33756] "Copy type" does not correctly detect existing file that is out of project structure

ReSharper

"Copy type" does not correctly detect existing file that is out of project structure

Created: 20 Dec 06 17:17 Updated: 01 Mar 08 15:46

Component/s:

Refactorings

Fix Version/s:

Future Versions

Security Level:

Everybody (All jira users)

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

File Attachments:

None

Image Attachments:

1. file already exists.JPG
(36 kb)

Build:

326

Description

« Hide

I was using the "copy type" refactoring to create a new type. Unfortunately, the resulting file name refers to a file that already exists on my harddisk. See attached image. The proposed action seems logical.However, it was not so in this case, as the file was not part of the project. Another logical option would be to suggest to overwrite the existing file.

So the request is to extend the dialog (as shown in the attached image) with an additional choice to overwrite the existing file.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Ilya Ryzhenkov - 30 Jan 07 17:01

I don't think we should have an option to overwrite the file, because it is potentially dangerous and can erase some important information. I think we should just issue appropriate error message and let developer erase the file automatically. Then we can have "Retry", "Cancel" buttons.

[ Permlink | « Hide ]

Erwin Derksen - 31 Jan 07 21:42

developers don't erase files automatically, they do so, manually

Tools can do this automatically. But you're absolutely right in stating that it is potentially dangerous. Although on the other hand, we're talking about a file that is not part of the project/solution. But the developer should absolutely confirm this action.

Up to Jetbrains, to decide how to proceed. I've said my words...