Dataloss when renaming file two times

[Xanadu333]

Hello everyone.

Microsoft has a lot of text editor on their different products and I have come to a way of working (which might not be the best of all in some cases) and it seems like using Visual Studio Code in a manner allows the customer, like myself, to be loosing its file progress when renaming a file.

This happened after I wanted to rename a java class, for example, “myclass.java” to “MyClass.java”.
Since the change lookup is case insensitive, they both are of equal names which will result in no name change, so you will have to rename the file to a temporary name in order to make your change.

Now the following process will come in to the bug to be fixed.

• Create a new file name “myclass.java”.
• Enter the following code into that file (replace the content if necessary):

public class myclass
{
    public myclass()
    {

    }
}

• Now save the file.
• Now add this method to the class:

...
    public void myMethod()
    {
        // My work in progress...
    }

• Now without saving this time. Rename the file using the right-click in the object-browser pane of the VSCode to “temporaryname.java”. You will see the file has the same content but with the new name.
• Now rename the file again like before to “MyClass.java”. Now, it will be taking the last saved file named “myclass.java” and take its content instead of taking the current file content. Therefore loosing all work in progress. In this case, the class myclass will no longer have the method myMethod(), and there will be an error from the intellisense since the class myclass does not equal MyClass.

Now I know that saving will fix all of this. BUT, Microsoft, as a reliable source for text editing, at least I would have liked a minimum of a prompt of “Are you sure you want to rename the file to "newNameFile"? The work in progress might be loss.”

This is very common for I to do this in other Microsoft text editing products and this seems to be a bug to be fixed. Allowing the customer to loose its progress without warning is a bug to me.

All thanks.

[lramos15]

Not sure if this is an explorer issue or a file system issue cc @bpasero .

Just assigned to me for now because the bot did

[bpasero]

This is an excellent bug report and no, this should not happen, sorry for that. Will have a look!

[VSCodeTriageBot]

This bug has been fixed in the latest release of VS Code Insiders!

@Xanadu333, you can help us out by commenting /verified if things are now working as expected.

If things still don't seem right, please ensure you're on version 03dd3c3 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.

Happy Coding!