| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Another PR which provides a simpler fix for those issues. Ideally this PR should handle the toRealPath() exception too. |
Sorry, something went wrong.
|
@johncrim I think that's two different things, although very close, to fix. This PR aims to fix the extended path on windows. |
Sorry, something went wrong.
Canonicalize Windows namespaced paths at internal filesystem identity boundaries. Valid namespaced drive and UNC paths identify the same filesystem objects as their non-namespaced spelling, so internal cache, permission, and module lookups should compare the canonical identity rather than the user-provided spelling. Only the two known filesystem-equivalent namespace forms are rewritten: \\?\C:\... and \\?\UNC\server\share\.... Other namespaced forms are preserved because they may refer to device or drive-relative semantics that are not equivalent to ordinary drive or UNC paths. Signed-off-by: jazelly <xzha4350@gmail.com>
|
After second thoughts and understanding to other mentioned issues, I think we should take care of them at the js layer to be safer. Closing this |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Canonicalize valid Windows namespaced drive and UNC filesystem paths by stripping the prefix in these 2 kinds
This is safe for ToNamespacedPath() because it resolves to the regular drive or UNC spelling before adding the namespace prefix back for Windows filesystem calls.
Fixes: #62446