g1tup
commented
5 years ago VS Code Explorer allows folder names illegal in Windows
Had the same issue with a folder name like "Scan 09.04." And subsequently found this:
"Do not end a file or directory name with a space or a period. Although the underlying file system may support such names, the Windows shell and user interface does not."
https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file#file-and-directory-names
For better illustration I reproduced this behavior and provide two screenshots:
Please escalate this issue as it is difficult - if not impossible - to get rid of these useless folders.
Thank you :-)
Issue Type: Feature Request
My colleague and I had an insanely embarassing and unforgetable experience today at work due to the lack of a feature involving trailing spaces in folder names.
I was teaching my colleague how to use Redux with React Native when we got an error in the console. Something along the lines: "Could not resolve module reducers. Path ./reducers not found."
I had encountered this issue many times before with previous versions of Expo in which the Metro Bundler cache would not update correctly and it would not recognize the creation of a new folder. I believed the problem to be related to the cache and my colleague and I spent half a day researching the issue on Google and StackOverflow.
Eventually, we realized that my colleague had accidentally included a space at the end of the folder name as follows: "reducers ". Not in the import statement, however.
There should undoubtedly be a feature in VSCode that enables a warning message by default for trailing spaces in both folder and file names.
Though I will admit, the laugh we got out of this was well worth the loss of time.
VS Code version: Code - OSS 1.30.2 (61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8, 2019-01-08T23:10:56.746Z) OS version: Linux x64 4.20.6-arch1-1-ARCH