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
The VFS should perform case-insensitive actions, which it seems to do. However, when querying the file system using methods which return string-paths for file/folder names, the names are returned in lower-case only, even for mixed-case file/folders. For example:
We add the folder FooBar: vfs.AddFolder("C:\\Hello\\FooBar");
When fetching this file, FooBar becomes foobar: vfs.FindFiles("C:\\Hello", "FooBar"); // => ["foobar"]
While this isn't technically a problem because Windows' FS handling is case-insensitive by default, it's conceivable that usercode may expect the case to be returned correctly (such as string comparisons for file/folder paths).
The text was updated successfully, but these errors were encountered:
A technique which may be applicable here was done in runtime/virtreg.js. See the resolve_path method which uses a dictionary to map original keys to their normalised values.
The VFS should perform case-insensitive actions, which it seems to do. However, when querying the file system using methods which return string-paths for file/folder names, the names are returned in lower-case only, even for mixed-case file/folders. For example:
We add the folder
FooBar
:vfs.AddFolder("C:\\Hello\\FooBar");
When fetching this file,
FooBar
becomesfoobar
:vfs.FindFiles("C:\\Hello", "FooBar"); // => ["foobar"]
While this isn't technically a problem because Windows' FS handling is case-insensitive by default, it's conceivable that usercode may expect the case to be returned correctly (such as string comparisons for file/folder paths).
The text was updated successfully, but these errors were encountered: