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
Hello, I have a exception for file not found on a particular case:
I have fileName like '..\filename' and path like 'c:\folder1\folder2', the file 'c:\folder1\filename and the path c:\folder1\folder2 exist, but if I do
I'm not sure this is something we intend to support. Traversing up negates the "safety" added by the second argument as it will have to check that directory; removing the need to do that is the very intent of the second argument (it was introduced to support shared hosting).
Really, the second argument should be thought of less as a "base path" and more of a "known good" path. If there are no permission errors to worry about, trueCasePathSync(path.resolve('c:\folder1\folder2', '..\filename')) would be the preferred usage.
Hello, I have a exception for file not found on a particular case:
I have fileName like '..\filename' and path like 'c:\folder1\folder2', the file 'c:\folder1\filename and the path c:\folder1\folder2 exist, but if I do
trueCase.trueCasePathSync('..\filename' ,'c:\folder1\folder2');
an exception is fired for file not found
The text was updated successfully, but these errors were encountered: