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
Switching between case-sensitive and case-insensitive operating systems can be a pain point. e.g. something like Configs.ParseFile("myFile.yaml") will work with a file named MyFile.yaml on case insensitive file systems but not on a case-sensitive one.
This can make certain errors only appear in production or when running on other systems.
There should be a global setting that controls case-sensitivity in filename and file path searching that defaults to true:
Configs.Settings.CaseInsensitiveFilenames = true;
And any file name or path manipulation in FileManager should respect this setting.
The text was updated successfully, but these errors were encountered:
Switching between case-sensitive and case-insensitive operating systems can be a pain point. e.g. something like
Configs.ParseFile("myFile.yaml")
will work with a file namedMyFile.yaml
on case insensitive file systems but not on a case-sensitive one.This can make certain errors only appear in production or when running on other systems.
There should be a global setting that controls case-sensitivity in filename and file path searching that defaults to true:
And any file name or path manipulation in
FileManager
should respect this setting.The text was updated successfully, but these errors were encountered: