Official release丨Visual Studio Code 1.68

Welcome to the May release of Visual Studio Code, which highlights the following:

▌Configure Display Language
The Configure Display Language command has been updated to include:

• The language name of the language.
• Available languages shows which languages are not installed on your computer, you select a language and it will be installed and applied automatically.
  

▌ Questions panel table view

We added a new feature for users to switch the view mode of the question panel between tree and table. In contrast to the tree view, the table shows the source (language service or extension) of each question, allowing the user to filter questions by source.

You can toggle the view UI using the "View as Table/View as Tree" button in the upper right corner of the problem panel, or use the "Problems: Default View Mode" setting to change the default view mode.

▌Deprecated extensions

An extension can be deprecated, in favor of another extension, or when its functionality is built into VS Code. VS Code will render deprecated extensions in the Extensions view as shown below.

• A deprecated extension that is no longer maintained.
  
• When an extension is deprecated in favor of another, VS Code does not allow users to install that extension.
  
• When a deprecated extension's functionality is built into VS Code, it can be enabled via a configuration setting.
  

VS Code will not automatically migrate or uninstall deprecated extensions, there will be a Migrate button to guide you to switch to recommended extensions.

▌Extended sponsorship

We now allow users to sponsor their favorite extensions. If an extension can be sponsored, VS Code will render a Sponsor button in the Extensions view Details page like this:

▌Use .gitignore to hide explorer files
File Explorer now supports parsing and hiding files excluded by .gitignore files. This can be enabled with the Explorer: Exclude Git Ignore (explorer.excludeGitIgnore) setting. This setting is used in conjunction with files.exclude to hide unwanted files from Explorer.

▌Git branch protection With the new git.branchProtection setting, you can configure which branches to protect. VS Code avoids committing directly on a protected branch, instead letting you create a new branch to commit to. You can use the git.branchProtectionPrompt setting for fine-tuning.

▌TypeScript Go to Source Definition
JavaScript (especially compiled JavaScript provided by many libraries) is more difficult to analyze than .d.ts. Trying to profile all JavaScript code under node_modules is slow, increases memory usage, and has many JavaScript patterns that the VS Code IntelliSense engine doesn't understand.

This is where the new Go to Source Definition command comes in. When you run this command from the editor context menu or command palette, TypeScript will try to track down the JavaScript implementation of the symbol and navigate to it.

▌VS Code for the Web Localization For VS Code for the Web, we decided to take an approach that is more in line with the way the web works today. For users who set their browser language to one of our main supported languages, vscode.dev will automatically translate. The languages we support are documented in the vscode-loc repository.

For example, to configure the display language in Microsoft Edge, you can go to Settings > Languages:

Over the next few months, we'll be enabling localization of extensions (both with and without VS Code. Stay tuned!)

▌Preview: Markdown link validation

When using Markdown, it's easy to mistakenly add invalid file links or images, however, you can only find these errors after viewing the Markdown preview or even publishing. VS Code's new Markdown link validation can help you catch these errors. With link validation, VS Code will analyze Markdown links to headers, images, and other local files. Invalid links will be reported as warnings or errors.

Click to view the original blog ~