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
Basically any glob which has no operators inside such as * or {} just returns the string as-is without any post-processing, even when it contains the wrong path separator. Note that the path must exist for it to not return zero results.
The result I expect is the same path I entered (not resolved or normalized or anything) just with the native path separator.
The text was updated successfully, but these errors were encountered:
NotWearingPants
changed the title
An glob without any globs returns forward slashes on Windows
A glob without any globs returns forward slashes on Windows
Sep 26, 2021
NotWearingPants
changed the title
A glob without any globs returns forward slashes on Windows
Any glob without any globs returns forward slashes on Windows
Sep 26, 2021
Usually and as per the documentation, input globs use forward slashes and the result paths use the native file separator.
But here are examples of globs on Windows which return forward slashes (a bug):
Basically any glob which has no operators inside such as
*
or{}
just returns the string as-is without any post-processing, even when it contains the wrong path separator. Note that the path must exist for it to not return zero results.The result I expect is the same path I entered (not resolved or normalized or anything) just with the native path separator.
The text was updated successfully, but these errors were encountered: