-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
vscode-uri escapes colon in drive letter #75027
Comments
Like which? Do you have a sample? |
What issues are those? |
If we use Also Chrome uses the format We can work around it on our end, this is more just a question about why it's done that way. |
I always only looked https://tools.ietf.org/html/rfc3986 and there is no clear word on how aggressive to encode. My guarantee is that we decode whatever gets encoded, e.g preserving the identify. The challenge is when urls as strings get send around esp to different systems or when uris are compared in string form. All of that wasn't part of the original work... We can consider making this change (I have already done some similar changes this milestone) but I am always afraid that vscode has persist uris as string that it compare such uris - as strings, not revising them first. |
Closing as designed, after the recent avalanche of regressions after some URI changes I am too scared to change more here. For the future we can consider adding another overload to the toString-function |
The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines. Happy Coding! |
We are trying to use vscode-uri in the debug adapter, and one issue is that vscode-uri uri-encodes the colon after the drive letter in a windows file uri which causes issues downstream.
I see #2990 (comment) but I'm worried that will just cause other issues by not encoding other characters. And I'm wondering why we do this by default, this file URI scheme spec calls out
file:///c:/foo
as being a valid file URI. https://tools.ietf.org/html/rfc8089The text was updated successfully, but these errors were encountered: