microsoft
/
vscode-docs
зеркало из https://github.com/microsoft/vscode-docs.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Add 1.56 social image

This commit is contained in:
gregvanl 2021-05-05 09:39:51 -07:00
Родитель d93c6adc1b
Коммит 8c14d10629
2 изменённых файлов: 17 добавлений и 14 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

3
release-notes/images/1_56/release-highlights.png Normal file
Просмотреть файл

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:b9f1a15e4a4664698f03ec173431e12e715b2f6af64e48614e2b4096839a98bc
size 36063

28
release-notes/v1_56.md
Просмотреть файл

@ -13,7 +13,7 @@ DownloadVersion: 1.56.0
Welcome to the April 2021 release of Visual Studio Code. The VS Code team has been busy this month working on several longer lead time updates so check out the [Preview features](#preview-features) section to learn what's upcoming. Here are some of the highlights included in this release:
* **[Improved hover feedback](#improved-action-hover-feedback)** - Helps you quickly find clickable buttons.
* **[Improved hover feedback](#improved-action-hover-feedback)** - Helps you quickly find clickable editor actions.
* **[Terminal profile improvements](#terminal)** - Create a custom default terminal profile.
* **[Debugger inline values](#inline-values-by-default-for-some-languages)** - Display variable values inline during debugging sessions.
* **[Notebook KaTeX support](#math-support-in-markdown-cells)** - Math support in Notebook Markdown cells.
@ -202,7 +202,7 @@ This will initially be visible only to a subset of users as we experiment with i
**Private Class Field Support**
[Private class fields](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields) are now visible and can be inspected in the debugger.
[Private class fields](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Classes/Private_class_fields) are now visible and can be inspected in the debugger.
## Notebooks
@ -210,7 +210,7 @@ This will initially be visible only to a subset of users as we experiment with i
You can now toggle the line numbers of a cell in current session temporarily from cell toolbar, or change the visibility of line numbers for all notebooks through setting `notebook.lineNumbers`.
![Toggle Line Number of a Cell](images/1_56/notebook-toggle-line-numbers.gif)
![Toggle line number of a cell](images/1_56/notebook-toggle-line-numbers.gif)
### Cell toolbar position per file type
@ -300,7 +300,7 @@ We have expanded the `walkthroughs` contribution for placing content on the Gett
In this milestone, we added experimental support for custom hovers in Activity bar and Panel. You can enable custom hovers using the setting `workbench.experimental.useCustomHover`.
![Custom Hover in Activity Bar & Panel](images/1_56/custom-hover.gif)
![Custom hover in Activity Bar and Panel](images/1_56/custom-hover.gif)
*Theme: [GitHub Light Theme](https://marketplace.visualstudio.com/items?itemName=GitHub.github-vscode-theme)*
*Product Icon Theme: [Fluent Icons](https://marketplace.visualstudio.com/items?itemName=miguelsolorio.fluent-icons)*
@ -309,7 +309,7 @@ In this milestone, we added experimental support for custom hovers in Activity b
As part of this release, we are previewing a new built-in extension, **Remote Repositories (RemoteHub)**, which allows you to instantly browse, search, edit, and commit to any GitHub repository directly from within VS Code without having to clone or have the repository locally. It is currently only available in the Insiders edition of VS Code.
#### Getting started
**Getting started**
To get started, run the **Open Remote Repository...** command from the Command Palette. From there, you can paste in any GitHub URL, or choose to search for a specific repository or pull request.
@ -319,18 +319,18 @@ To get started, run the **Open Remote Repository...** command from the Command P
Once you enter a URL or choose a repository or pull request, VS Code will open a new workspace for that repository. The remote status indicator, on the left side of the Status bar, shows the connected remote provider name, for example GitHub, for the remote repository.
![Remote Repositories Demo](images/1_56/remote-repositories.gif)
![Remote Repositories Demo showing various source control operations](images/1_56/remote-repositories.gif)
*Theme: [Amethyst Dark Theme](https://marketplace.visualstudio.com/items?itemName=eamodio.amethyst-theme)*
#### Features
**Features**
* Instantly open any GitHub repository without cloning or having the repository locally.
* Easily edit and contribute to any GitHub repository - directly commit your changes to GitHub, or open a pull request.
* Continue in another environment - via the **Continue on...** command (accessible from the Command Palette or the remote indicator quick pick menu).
* Clone the repository locally
* Clone the repository into a container - requires the [Remote - Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension
* Provides a familiar user interface to working on local repository (see [limitations](#limitations) below).
* Provides a familiar user interface to working on local repository (see "Limitations" below).
* **Explorer** - open, copy, move, rename, and delete files and folders
* **Search** - fast full-text search<sup>*</sup>
* **Source Control** - stage and commit your changes, as well as many other source control actions
@ -340,7 +340,7 @@ Once you enter a URL or choose a repository or pull request, VS Code will open a
* Work on different branches simultaneously - each remote branch is treated like a separate worktree (in Git parlance), meaning that any changes you make are isolated to that branch. You don't need to stash your changes just to switch to a new branch to checkout a PR or start on a new work item. And when you go back to the previous branch your changes will still be there.
* Install the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension, and quickly view, explore, and checkout pull requests, view and start working on issues.
#### Limitations
**Limitations**
* Limited language intelligence - many language servers don't yet understand this virtualized environment. TypeScript supports single file intelligence for remote repositories.
* Limited extension support - as with language servers, many extensions don't work with remote repositories. Extensions can opt-out and will then not be activated for virtual workspaces. See the [Extension authoring section](#extension-authoring-) below for more details.
@ -349,7 +349,7 @@ Once you enter a URL or choose a repository or pull request, VS Code will open a
* Debugging - not supported.
* Tasks - not supported.
#### Tell us what you think
**Tell us what you think**
We are very excited for you to play with **Remote Repositories (RemoteHub)** and can't wait for your thoughts and feedback. We are just getting started on this journey, so expect the feature set to grow and the limitations to shrink as we continue development. We will also be expanding the set of supported providers. GitHub is just the first provider we are supporting, with support for Azure Repos coming soon too.
@ -369,7 +369,7 @@ In last milestone's release notes, we shared our work on Workspace Trust specifi
You can enable the feature with the following setting `security.workspace.trust.enabled`. Once enabled, you will see the following dialog when opening folders in VS Code.
![Workspace Trust Startup Dialog](images/1_56/trust-dialog.png)
![Workspace Trust startup dialog](images/1_56/trust-dialog.png)
This dialog is important for allowing the user to make a decision early and understand the impact of their decision. Once you understand the feature, you may want to customize when to display the dialog using the setting `security.workspace.trust.startupPrompt`.
@ -423,7 +423,7 @@ There will be a transition period until extensions have adopted the new `virtual
Extensions can now contribute to the remote indicator menu:
![Remote Indicator](images/1_56/remote-indicator.png)
![Remote indicator on the left of the Status bar](images/1_56/remote-indicator.png)
The `statusBar/remoteIndicator` menu contribution point adds a command to the remote indicator menu.
@ -522,7 +522,7 @@ We've added the following new icons to our [codicon library](https://code.visual
* `terminal-ubuntu`
* `wand`
![List of updated codicons](images/1_56/codicons.png)
![List displaying updated codicons with their names](images/1_56/codicons.png)
### Keybinding label colors
@ -748,7 +748,7 @@ This new strictness rule should also help us catch some common programming mista
### Windows installers consolidated in Windows Package Manager
We have updated our [Windows Package Manager](https://docs.microsoft.com/windows/package-manager/) publishing pipeline to publish our user and system installers for `arm64`, and to adopt the [v1 package manifest schema](https://github.com/microsoft/winget-cli/blob/master/doc/ManifestSpecv1.0.md), allowing us to consolidate the user and system installers for `x86`, `x64` and `arm64` into a single manifest. Users can pick between the user and system installers using the `--scope` parameter when [installing](https://docs.microsoft.com/windows/package-manager/winget/install) a package or using the [winget CLI settings](https://aka.ms/winget-settings).
We have updated our [Windows Package Manager](https://docs.microsoft.com/windows/package-manager/) publishing pipeline to publish our user and system installers for `arm64`, and to adopt the [v1 package manifest schema](https://github.com/microsoft/winget-cli/blob/master/doc/ManifestSpecv1.0.md), allowing us to consolidate the user and system installers for `x86`, `x64` and `arm64` into a single manifest. Users can pick between the user and system installers using the `--scope` parameter when [installing](https://docs.microsoft.com/windows/package-manager/winget/install) a package or using the [winget CLI settings](https://aka.ms/winget-settings#scope).
## Documentation