Tag: VSCode

tags

Utilize command URIs for efficient documentation access in Visual Studio Code

One key benefit of using command URIs in your Visual Studio Code extensions is the ability to trigger commands from links in the editor. Those links can be added to various places in the extension, such as hover cards, notifications, webviews, and completion item details. info A command URI starts with the command: scheme followed by the command name and optional arguments.

Read more

Integrate your Visual Studio Code extension in the Source Control Management input

For a new Visual Studio Code extension called CommitHelper, I wanted to integrate the extension in the Source Control Management (SCM) input. The extension should provide a list of predefined commit messages from which the user can select by using a slash / in the input field. Show image Source Control Management Input I got the idea from the GitHub Pull Requests extension that provides a similar experience when tagging/linking issues.

Read more

Adding a support link for your Visual Studio Code extension on the marketplace

While preparing a new release for Front Matter CMS, I noticed an API call to GitHub failing from the Visual Studio Code marketplace. While looking into it, it requested a SUPPORT.md file in the repository’s root. Show image VSCode Marketplace - Call for the SUPPORT.md file The VSCode Marketplace uses the following API format: https://api.

Read more

Things to know when using custom icons for Visual Studio Code commands

You can specify an icon when adding commands to your Visual Studio Code extension. These icons are rendered when you register the commands, such as the explorer title bar, document title bar, and more. info More info on registering command can be found in the VSCode documentation. You have three options for specifying the icon:

Read more

Organize and Optimize: Splitting Visual Studio Code Extension Settings into Multiple Categories

I have always been adding my Visual Studio Code extension settings to the contributes.configuration object, but I was missing a way to organize the settings in multiple sections/groups. That way, the end user gets a better overview of all settings grouped by their category. When reading the VSCode contributes.configuration schema documentation, I spotted the following: “This section can either be a single object, representing a single category of settings, or an array of objects, representing multiple categories of settings.

Read more
Back to top