-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Fix path.relative UNC path result #8523
Conversation
When the result of a path.relative() is an absolute UNC path, it should include the leading backslashes. Fixes: nodejs#8444
a3827ed
to
5712f33
Compare
@mscdex please review. |
LGTM, CI failure on ARM is unrelated. |
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.
LGTM
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.
LGTM
Landed in c1e47ed! Thank you! |
hey all... does this seem like a good candidate for a backport? |
Has this been in a Current release yet? But yeah, I would say so. |
@addaleax has not been, but was mostly auditing for labeling |
@thealphanerd @addaleax This PR isn't relevant for v4.x since the |
@mscdex thanks for clarifying! |
Checklist
vcbuild test nosign
(Windows) passes(Some tests failed, but they're unrelated: the failures repro without this change.)
Affected core subsystem(s)
path
Description of change
When the result of a path.relative() is an absolute UNC path, it should
include the leading backslashes.
Fixes: #8444