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
"Copy Remote File Url" url-encodes the URL #1202
Comments
This is causing a lot of issue for my firm's hosted bitbucket. |
Workaround I use for now is to use the Open File on Remote command and copy the URL from the browser. That seems to avoid URL-encoding. |
I added the encoding to deal with spaces in the file path (otherwise it would break the url). Maybe I just need to either encode just that, or just decode |
Can you please verify this fix in the latest insiders version? You can install the insiders version from here. |
Hmm, just installed the insider version. My URLs are still encoded:
expected:
|
Hey @eamodio it seems to be fixed on my end after disabling the GitLens and installing the GitLens Insiders.
@ThibaultJanBeyer probably try disabling the stable release version?
…On Mon, 30 Nov 2020 at 18:39, Thibault Jan Beyer ***@***.***> wrote:
Hmm, just installed the insider version. My URLs are still encoded:
https://stash.int.company.net/projects/company/repos/company-app/browse/services%2Fsome-service%2Fsrc%2Fapi%2Fadmin%2Ffoo%2Fget%2Findex.js?at=AM-632-post-internal-endpoint#3
expected:
https://stash.int.company.net/projects/company/repos/company-app/browse/services/some-service/src/api/admin/foo/get/index.js?at=AM-632-post-internal-endpoint#3
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1202 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACYRVIVIVQ3Q4Q4WOXLMKF3SSNY55ANCNFSM4T7T3ZNA>
.
|
@ThibaultJanBeyer Are you sure you were testing on the latest insiders? I can't see how you'd get that type of encoding given the changes I've made. |
confirm: insiders version fixes the escaping problem. |
@eamodio I uninstalled and re-installed the insiders version. Now the encoding seems correct. Thank you! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to Reproduce:
%2F
instead of/
)I think this started happening with v11.0.0. The url-encoded version still works but is uglier, for example:
The text was updated successfully, but these errors were encountered: