We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Test for #46256:
Complexity: 3
Authors: @joaomoreno
First, make sure your extension sets "enableProposedApi": true in its manifest. Then, get the latest definitions:
"enableProposedApi": true
engine.vscode
*
package.json
npm run postinstall
Uris directed towards extension vscode.git, for example, all share the following prefix:
vscode.git
{scheme}://vscode.git
(with vscode.git being the extension id).
For example, for VS Code Insiders, these are valid Uris which will be handled by the git extension's protocol handler:
vscode-insiders://vscode.git vscode-insiders://vscode.git/ vscode-insiders://vscode.git/status vscode-insiders://vscode.git/clone?url=foobar
As an extension author, you can:
onUri
Here's how you can test Uri opening:
explorer URI
open URI
xdg-open URI
You can also open a URL from the command line with --open-url URL. This can be used simultaneously with --enable-proposed-api.
--open-url URL
--enable-proposed-api
The text was updated successfully, but these errors were encountered:
I've removed Linux, since URL handlers are not yet supported by Code: #48528
Sorry, something went wrong.
No branches or pull requests
Test for #46256:
linux: @ramya-rao-aComplexity: 3
Authors: @joaomoreno
Setup
First, make sure your extension sets
"enableProposedApi": true
in its manifest. Then, get the latest definitions:engine.vscode
property to*
inpackage.json
npm run postinstall
URI Format
Uris directed towards extension
vscode.git
, for example, all share the following prefix:(with
vscode.git
being the extension id).For example, for VS Code Insiders, these are valid Uris which will be handled by the git extension's protocol handler:
Test Details
As an extension author, you can:
onUri
to be activated when a Uri for that extension is opened. This should work in all cases:Here's how you can test Uri opening:
explorer URI
in a command promptopen URI
in a shellxdg-open URI
in a shellYou can also open a URL from the command line with
--open-url URL
. This can be used simultaneously with--enable-proposed-api
.The text was updated successfully, but these errors were encountered: