liximomo / vscode-sftp

Super fast sftp/ftp extension for VS Code
MIT License
1.5k stars 256 forks source link

Changing the case of a folder is ignored #974

Open sekra24 opened 2 years ago

sekra24 commented 2 years ago

Do you read the FAQ?

Describe the bug If I change a folder/file name from lowercase to uppercase and vice versa. And upload it with "save file" it ignores the case changing. If I upload the folder/file with right click > upload folder it works. So it seems like there is a caching in the "upload on save" method.

To Reproduce Steps to reproduce the behavior:

  1. Save a file so it get's uploaded. e.g. /Api/Api.php
  2. Change the folder case to /api/
  3. Save the Api.php file again

Expected behavior The extension should upload the file to the folder with the correct case.

MaksimUrasov commented 2 years ago

I have same behaviour:

File on host is located in Api/Test.php, when edited and saved, gets loaded to remote server to folder with lowercase folder: api/Test.php. Uploading whole folder works fine, but when the Test.php file on host gets saved, an additional lowercase "api" folder is created with my updated Test,php inside. That means I get two folders on remote: "Api" with old file and "api" with updated file.

dennisbohn commented 2 years ago

I am having the same problem with files. Even uninstall and reinstall the extension didnt solve the problem. When I save the file it uploads the old lowecase version of my file.

sekra24 commented 2 years ago

Any update on this? Seams like this is still a problem and it is really annoying. Is there any fix for this?

Thank you.

firgon commented 1 year ago

Same isssue for me. I upload once file.php then change my local file into File.php, SFTP always upload my new file (with new content) into remote file.php file... That's really annoying.

migliori commented 1 year ago

Still the same issue for me. In my opinion, this is a major bug, which can cause a lot of time loss because it is not always easy to find the cause. You upload, the content doesn't change: is it a cache problem? or a path problem?

Solving this problem should be a priority. Or at least explain how to clear the cache of SFTP.