猫史档案馆

Product icon themes

Visual Studio Code contains a set of built-in icons that are used in views and the editor, but can also be used in hovers, the status bar, and by extensions. These icons are product icons as opposed to file icons, which are displayed next to file names throughout the UI.

The product icons that ship with VS Code are contained in the Codicon icon font and are used for the default product icon theme. Extensions can now provide new product icon themes to redefine these icons and give VS Code a new appearance.

The Product Icon Themes documentation has more details and there is a Product Icon Theme Sample.

TypeScript/JavaScript symbol search across all open projects

When using TypeScript 3.9+, VS Code's workspace symbol search now includes results from all opened JavaScript and TypeScript projects by default. We previously only searched the project of the currently active file.

This is controlled by the new "typescript.workspaceSymbols.scope" setting. To revert to the old behavior, set: "typescript.workspaceSymbols.scope": "currentProject".

Improved links in the terminal

Links in the terminal have undergone an overhaul, changing out the backing system for a much more robust implementation that enables:

• The use of the editor's link detection for better web and file:// link detection.
• Folder link support, either opening the folder in the Explorer or opening a new VS Code window.
• Different link actions for different link types, falling back to "word" links that search the workspace (based on the terminal.integrated.wordSeparators setting).
• Similar link highlighting and hover experience to the editor.

Theme: Topaz (Dim)

A list of known issues is available in this query.

Dynamic view icons and titles

This milestone, we continued on the work to make the layout more flexible. Moving views around the workbench allows you to create new icons in the Activity Bar or new tabs in the Panel. To make it easier to understand what is held in one of these newly created view containers, we have updated the logic to be easier to understand.

Now, when you have a custom container, we will inherit the title and icon from the first visible view. This will allow you to change it by rearranging the views. For containers that are built-in or from extensions, we will try to preserve this icon as long as possible. Below when a new view is placed at the top of the view container, its icon and title are updated.

Lastly, you can now move your custom containers around with all of the containing views in one movement. The short video below shows dragging a Terminal and Output view combination into the Activity Bar.

Contributions to extensions Remote Development

Work continues on the Remote Development extensions, which allow you to use a container, remote machine, or the Windows Subsystem for Linux(WSL) as a full-featured development environment.

Feature highlights in 1.45 include:

• Remote - Containers: Provide container configuration recommendations.
• Remote - Containers: WSL2 Docker and Podman engines support.
• Remote - Containers: New devcontainer.json variables for local and container folders.

You can learn about new extension features and bug fixes in the Remote Development release notes.

GitHub Pull Requests and Issues

Formerly named "GitHub Pull Requests", the GitHub Pull Requests and Issues extension has been letting you manage and review pull requests from within VS Code for over a year now. Now, the extension as been expanded to include support for GitHub Issues.

Issue support includes:

• Hovers for #-referenced issues and @-mentioned users.
• Inline completion suggestions for issues and users.
• An Issues view where you can use custom queries.
• An action to start working on an issue, which creates a branch and populates the commit message.

There is also new repository support:

• Clone a repository using a remote source provider.
• Publish a repository to GitHub.

The short video below illustrates publishing to a new private repository on GitHub, with an option to browse the repo on GitHub once the files have been successfully uploaded.

For more information, you can read the recent GitHub Issues Integration blog post and Working with GitHub documentation