Visual Studio Code developers can now sponsor their favorite extensions — Visual Studio Magazine
Visual Studio Code developers can now sponsor their favorite extensions
Microsoft now allows Visual Studio Code users to financially sponsor the authors of their favorite extensions.
“VS Code now allows users to sponsor their favorite extensions,” the development team said when announcing the regular monthly (May 2022) VS Code update – bringing it to v1.68 – while pointing to this illustrative graphic:
Pressing the sponsor button for participating extensions takes the user to the URL of a sponsorship page where contributions can be made and sponsors can be listed along with other information.
Extension authors can sign up for the referral program through a new
sponsor field in an extension
package.json settings file where the URL can be provided, after which the Sponsor button will appear in the Extension Details page as shown above.
Sponsorship functionality is similar to that used by GitHub, as explained in the “A New Way to Contribute to Open Source” documentation.
Other highlights of the May 2022 Update as presented by Microsoft, with links for more information, include:
- Configure display language — View installed and available language packs in their language: This command now displays the language name in that language. Developers can also see which languages are not installed on their machines in an Available Languages section, where selecting a language will automatically install and apply it.
- Viewing the Issues panel table — Display errors and warnings as a table to quickly filter their source: Developers can now switch the Issues panel display mode between a tree and a table. “Compared to the tree view, the table shows the source (language service or extension) of each issue, allowing users to filter issues based on their source.”
- Deprecated extensions — Find out if an extension is deprecated or needs replacing: New support for deprecated extensions in VS Code makes it easy for developers to deprecate an extension. They may abandon it in favor of another extension or even when its functionality is integrated into VS Code. The Extensions view will now show the status of extensions: obsolete and unmaintained; deprecated in favor of another extension, which prevents installation of the extension; deprecated with built-in editor features. Extensions will not be automatically uninstalled or migrated, although a Migrate button may help with the latter.
- Hide files from explorer using .gitignore — Reuse your existing
.gitignoreto hide files in explorer: file explorer can now scan and hide files excluded by a
.gitignorefile, activated via a new explorer: Exclude Git Ignore (
explorer.excludeGitIgnore) parameter that works alongside
files.excludeto hide junk files from explorer.
- Terminal color and contrast improvements — Find the corresponding background color, minimum contrast ratio:
- Look for matching background color: A colored background is now the default for themes when highlighting matches and the overall experience should resemble that of the editor.
- Contrast and minimum contrast ratio improvements: The contrast in the terminal has been improved to align the appearance of the terminal closer to that of the editor. Additionally, a new minimum contrast ratio feature dynamically changes the foreground of text to improve visibility.
- Protecting the Git branch — Branch protection available directly in VS Code: a new
git.branchProtectionThe setting can configure specific branches to be protected, after which VS Code will avoid directly committing to the protected branches and letting developers create a new branch to commit to instead.
- VS Code for web localization — vscode.dev now matches your browser language: Developers who set their browser to one of the major languages supported in the web version — vscode.dev — will automatically see translations applied in that language. Supported languages are listed in the vscode-loc repository.
- Development Container Specification — Learn more about the evolution of the Developer Container Specification: Work continued on the Developer Container Specification, which “looks to find ways to enrich existing formats with settings, tools, and development-specific configuration commons while providing a simplified, non-orchestrated single container option – so they can be used as coding environments or for continuous integration and testing.” This work included the release of an open-source CLI as a reference implementation for the specification, as well as a GitHub action and Azure DevOps task that are now available to run a repository’s development container in integration builds continuous (CI).
- Preview: Markdown Link Validation — Detects broken links to headers, images, and files: New experimental Markdown link validation can help catch errors like adding a file link or image reference invalid by forgetting that the filename used a – (dash) instead of a _ (underscore), for example, or in cases where a linked file was moved to another directory.
All of the above and many more new features, functionality, tweaks, and fixes are explained in much more detail in the announcement post.
David Ramel is an editor and writer for Converge360.