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
I am using vscode.env.openExternal and vscode.Uri.parse to open external URL in the browser.
My problem is that my URL contains '%2F' (which is the escaped value of '/') in its path (e.g., something like https://aaa/bbb%2Fccc).
It seems the Uri.parse unescapes the URL and than escape it again in openExternal, however:
Yes, this is the unfortunate truth. You will find some duplicates of this issue and honest, good attempts in fixing them. Which I all had to revert because too many extensions depend on the current, broken behaviour. It is a mess and unfortunately too late to properly fix. The current strategy is to allow string in addition to Uri in some places. See #85930 and issues linked from there
@jrieken thanks for the answer.
I think even adding an "escape" flag to the parse function which its default is true, or creating a new fixed URI type, to avoid breaking to current behavior would be a major improvement.
I am using
vscode.env.openExternal
andvscode.Uri.parse
to open external URL in the browser.My problem is that my URL contains '%2F' (which is the escaped value of '/') in its path (e.g., something like https://aaa/bbb%2Fccc).
It seems the Uri.parse unescapes the URL and than escape it again in openExternal, however:
(Assuming the builtins unescape and escape are used)
And thus, it removed the escaping of '%2F' and opening the wrong page in the browser.
Thanks
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: