-
-
Notifications
You must be signed in to change notification settings - Fork 473
Exposing Whitelisted Protocols to User Settings #1401
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
base: main
Are you sure you want to change the base?
Conversation
bf9e06c
to
6edcbb3
Compare
Thanks! Could you please update your commit message to match the commit style guidelines? |
Do not close and reopen multiple pull requests for the same thing, even to fix the commit structure; you can always fix the commit structure by rebasing and force-pushing your existing branch. |
6edcbb3
to
084620f
Compare
I adjusted the commit message to match the style guide. |
Is there anything left to do on this PR? |
87f4cff
to
f56c2d0
Compare
f56c2d0
to
d270d56
Compare
f21fa7d
to
dfe3839
Compare
@andersk @timabbott can you take a look if there's anything missing here that avoid a merge? |
I think we'd need documentation for how users can decide which protocols they can safely add there. |
Totally makes sense, i'm just unsure where to document the setting.json 's new key. Could you point me to where i shall add the information then i'm happy to add it there too |
A new file seems fine. I'd call it |
e333a68
to
d1b0d88
Compare
Allright i added a customize-link-protocols.md to docs/howto :) |
Adding config option to set protocols in the config that are whitelisted to be opened directly. The behaviour is documented in docs\howto\customize-link-protocols.md.
3158084
to
d244c9c
Compare
What's this PR do?
It exposes the whitelisted protocols list so users can add additional protocols that should not use the link wrapper.
Adresses Issue: #1284
You have tested this PR on: