-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
path: update win32 toNamespacedPath to support device namespace paths #54367
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #54367 +/- ##
==========================================
+ Coverage 87.09% 88.23% +1.14%
==========================================
Files 648 651 +3
Lines 182216 183895 +1679
Branches 34965 35847 +882
==========================================
+ Hits 158704 162267 +3563
+ Misses 16785 14913 -1872
+ Partials 6727 6715 -12
|
lib/path.js
Outdated
@@ -687,6 +707,19 @@ const win32 = { | |||
if (typeof path !== 'string' || path.length === 0) | |||
return path; | |||
|
|||
// Check if the path matches any device pattern | |||
if (ObjectValues(windowDevicePatterns).some((pattern) => pattern.test(path))) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be faster if the object was an array?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, you're correct. My local benchmarks confirm that using an array is indeed faster than using an object. Thank you very much for your thorough review. I will take this and apply the changes accordingly
5000736
to
d347f33
Compare
lib/path.js
Outdated
@@ -180,6 +180,25 @@ function glob(path, pattern, windows) { | |||
}); | |||
} | |||
|
|||
// Regular expressions to identify special device names in Windows. | |||
// Ref: https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea | |||
// COM to AUX (e.g., COM1, LPT1, NUL, CON, PRN, AUX) are reserved OS device names. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// COM to AUX (e.g., COM1, LPT1, NUL, CON, PRN, AUX) are reserved OS device names. | |
// | |
// COM to AUX (e.g., COM1, LPT1, NUL, CON, PRN, AUX) are reserved OS device names. |
This might help to separate the ideas
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're absolutely right. Moreover, the code I recently added is currently checking all regular expressions in the device namespace, which has significantly reduced performance. As you suggested, I will try to improve performance by distinguishing between special devices and reserved devices during the inspection. Thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added comments to differentiate between reserved and non-reserved device names, explaining the differences between regular expressions like /([\\/])?(COM\d+)$/i
and /^(PHYSICALDRIVE\d+)$/i
. While I tried to maintain performance while addressing the issues, I couldn't find a way to do so effectively because reserved device names can also appear in paths (e.g., C:/path/COM1
). If anyone has a better solution that maintains performance while resolving this, I welcome suggestions.
I believe this is already being fixed in #54224 |
Thank you for let me know sir. I'll close this PR |
sir Im bit confused that #54224 seems to be focused on fixing an issue where a trailing backslash was incorrectly added in the |
I would work on this issue after finishing my current work. So, I reviewed this PR. This PR fixes a different problem than #54224 and LGTM. I think the author can continue working on this by reopening it. |
I believe this PR could fix #54161 as well. The |
Thank you for your valuable feedback. I initially included only |
9b397f6
to
aed9a78
Compare
Note that |
aed9a78
to
ee89dc7
Compare
Thank you for let me know. I just updated C++ implementation as well. |
09f9091
to
0f8415f
Compare
@targos I made the changes based on your feedback. Could you review this PR when you have a moment? |
0f8415f
to
fb92220
Compare
19f95e2
to
fb05e6e
Compare
Could you update the doc also? |
fb05e6e
to
15ecd34
Compare
Of course. Thank you for let me know. I updated the doc also according to your feedback. |
15ecd34
to
e04d346
Compare
e04d346
to
9eb494a
Compare
Updated the win32
toNamespacedPath
function to support device namespace paths as per #54180 and #54161.url.pathToFileURL
was not modified since device namespace paths are not valid file URIs.