You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.
I named a file ObjectAction.js and deployed it over SFTP. After that, I renamed it to objectaction.js. When I deploy it after that, it's still deployed as ObjectAction.js, and the server side scripts cannot import it because of this. Restarting VSCode doesn't help.
Actual behavior
The file renamed from CamelCase to lowercase after deployment, still deploys as CamelCase.
Expected behavior
The renamed file should be deployed with exactly the new name, even if it's just a character case change.
Steps to reproduce
Create a file in VSCode with a CamelCase name (e.g. "ObjectAction.js")
Deploy it with Ctrl+Alt+F over SFTP
Rename it to the same name, but lowercase (e.g. "objectaction.js")
Deploy it again
Check the server side to see if the file is deployed with the new name
Logs
this is the log when I deploy the file with the lowercase name:
Description
I named a file ObjectAction.js and deployed it over SFTP. After that, I renamed it to objectaction.js. When I deploy it after that, it's still deployed as ObjectAction.js, and the server side scripts cannot import it because of this. Restarting VSCode doesn't help.
Actual behavior
The file renamed from CamelCase to lowercase after deployment, still deploys as CamelCase.
Expected behavior
The renamed file should be deployed with exactly the new name, even if it's just a character case change.
Steps to reproduce
Logs
this is the log when I deploy the file with the lowercase name:
Your environment
Additional comments
Note: when I deploy the whole folder, the file deploys with the correct name. The bug only happens if I deploy the single file.
The text was updated successfully, but these errors were encountered: