shrink some images
This commit is contained in:
Greg Van Liew
Родитель
d61276428e
Коммит
903d2dd097
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:43b1a5fa9d979da4b5a8875c4f35028c7420cda5b01b9349f66aa44aa14d610d
|
||||
size 64741
|
||||
oid sha256:c1150160431b28fce825922b52a9096d8495a3e7c4d7aa03683b096eb243e3a6
|
||||
size 13468
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:78c4bbb09424e895a5749ef700da402bfc5b3e57f59ba30bc9c5859026348741
|
||||
size 299459
|
||||
oid sha256:f3a203a6657ddf3e88c4a8a175e508ae2a03819c431af58e38f235ef5f6d17e5
|
||||
size 273456
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:003da5b34d3019cca9f9119946f9580a5861ec17ac05461614aff76f77235747
|
||||
size 67189
|
||||
oid sha256:ea8fcd3bb62bf5e350e98a67326321bb71daf3b656a784879e2909d23e27f7a9
|
||||
size 57249
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ If you find issues or have suggestions, you can enter them in the [VS Code repos
|
|||
|
||||
VS Code now shows a prompt before opening outgoing links.
|
||||
|
||||
|
||||
|
||||
|
||||
You can open the link directly or trust specific domains to bypass this prompt. With the **Configure Trusted Domains** button or command, you can enable/disable link protection for specific domains or all outgoing links.
|
||||
|
||||
|
|
@ -66,7 +66,7 @@ There are two new when clause contexts for conditionally binding keyboard shortc
|
|||
* `activeEditorGroupIndex` - A number starting from `1` reflecting the position of an editor group in the editor grid. The group with index `1` will be the first in the top left corner.
|
||||
* `activeEditorGroupLast` - Will be `true` for the last editor group in the editor grid.
|
||||
|
||||
**Note:** See https://code.visualstudio.com/docs/getstarted/keybindings#_when-clause-contexts for a full list of when clause contexts.
|
||||
**Note:** See [keybinding documentation](https://code.visualstudio.com/docs/getstarted/keybindings#_when-clause-contexts) for a full list of when clause contexts.
|
||||
|
||||
### Updated cancel search icon
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ In the 1.37 release, we added a **Preserve Case** option to the editor's Find/Re
|
|||
|
||||
There is also a new case preservation mode for hyphen-separated words.
|
||||
|
||||
|
||||
|
||||
|
||||
### Explorer improvements
|
||||
|
||||
|
|
@ -100,7 +100,7 @@ We have improved the process of creating top-level files and folders in the Expl
|
|||
|
||||
**Open file and preserve focus**
|
||||
|
||||
It is now possible to open a file in preview from the Explorer while keeping focus in the Explorer. The new command is `filesExplorer.openFilePreserveFocus` and by default, it can be triggered via the `kbstyle(space)` key.
|
||||
It is now possible to open a file in preview from the Explorer while keeping focus in the Explorer. The new command is `filesExplorer.openFilePreserveFocus` and by default, it can be triggered via the `kbstyle(Space)` key.
|
||||
|
||||
**Explorer file naming**
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ The layout engine of the workbench has been rewritten to use the same grid widge
|
|||
|
||||
The new engine provides more flexibility for the workbench layout in the future. For now, we see this manifest itself with the ability to hide the editor area. There is a new command available with the grid layout, **Toggle Editor Area**. This will hide the editor area and allow the panel to take over completely. The **Toggle Maximized Panel** command has the same effect now. This means that a maximized panel is now truly maximized without the tiny gap previously left of the editor.
|
||||
|
||||
|
||||
|
||||
|
||||
The editor will automatically reappear if you try to open a file from anywhere such as the panel or sidebar.
|
||||
|
||||
|
|
@ -134,13 +134,13 @@ We continue to fix [accessibility issues](https://github.com/microsoft/vscode/is
|
|||
|
||||
You can now customize how many visible lines to display around the cursor while moving the cursor towards beginning or end of a file by setting `editor.cursorSurroundingLines`. In the Vim editor, this feature is called `scrollOff`.
|
||||
|
||||
|
||||
|
||||
|
||||
### Multi-line search in Find
|
||||
|
||||
The editor Find control now supports multiple line text search and replace. By pressing `kbstyle(Ctrl+Enter)`, you can insert new lines into the input box.
|
||||
|
||||
|
||||
|
||||
|
||||
### Copy and Revert actions in the inline diff editor
|
||||
|
||||
|
|
@ -150,7 +150,7 @@ There are new actions for copying or reverting deleted content when using the in
|
|||
* Copy a specific line
|
||||
* Revert the change
|
||||
|
||||
|
||||
|
||||
|
||||
### Global Search minimap decorations
|
||||
|
||||
|
|
@ -195,7 +195,7 @@ We thank MDN documentation team for their effort in curating [mdn-data](https://
|
|||
|
||||
VS Code now ships with TypeScript 3.6.2. This major update brings some TypeScript language improvements—including [stricter generators](https://devblogs.microsoft.com/typescript/announcing-typescript-3-6/#stricter-generators) and [support for `import.meta`](https://devblogs.microsoft.com/typescript/announcing-typescript-3-6/#import-meta-support-in-systemjs), as well as some new tooling features for both JavaScript and TypeScript. As always, this release also includes a number of important bug fixes.
|
||||
|
||||
You can read more about the TypeScript 3.6 features on the [TS 3.6 blog post](https://devblogs.microsoft.com/typescript/announcing-typescript-3-6/)
|
||||
You can read more about the TypeScript 3.6 features on the [TS 3.6 blog post](https://devblogs.microsoft.com/typescript/announcing-typescript-3-6/).
|
||||
|
||||
### Add missing await quick fix
|
||||
|
||||
|
|
@ -229,7 +229,7 @@ With TypeScript 3.6, our IntelliSense now only uses the immediately preceding JS
|
|||
|
||||
From the Variables view, it is now possible to create data breakpoints that will get hit when the value of the underlying variable changes. Just like other breakpoints, data breakpoints can be disabled/enabled and removed in the Breakpoints view.
|
||||
|
||||
|
||||
|
||||
|
||||
Please note that data breakpoints require specific support by an underlying runtime or debugger, and we expect only a few debug extensions like C++ and C# (but not Node.js) to opt into this feature in the future. For this release, only our example debugger [Mock Debug](https://marketplace.visualstudio.com/items?itemName=andreweinand.mock-debug) "mocks" data breakpoints.
|
||||
|
||||
|
|
@ -255,9 +255,9 @@ When launching a debug target in the Integrated Terminal, VS Code now respects t
|
|||
|
||||
### Helping webview extensions add a content security policy
|
||||
|
||||
We've identified a number of extensions that create [Webviews](https://code.visualstudio.com/api/extension-guides/webview) that don't have a [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP). While this does not present an immediate concern, all webview should have a content security policy as a good security best practice. This iteration, we've [started to open issues](https://github.com/microsoft/vscode/issues/79340) against these extensions to make them aware of the issue.
|
||||
We've identified a number of extensions that create [Webviews](https://code.visualstudio.com/api/extension-guides/webview) that don't have a [Content Security Policy](https://developer.mozilla.org/docs/Web/HTTP/CSP). While this does not present an immediate concern, all webview should have a content security policy as a good security best practice. This iteration, we've [started to open issues](https://github.com/microsoft/vscode/issues/79340) against these extensions to make them aware of the recommendation.
|
||||
|
||||
If you are interested make some of the extensions you use everyday a bit more secure, take a look over [this issue](https://github.com/microsoft/vscode/issues/79340) and submit PRs to help them out.
|
||||
If you are interested in making some of the extensions you use everyday a bit more secure, take a look at [VS Code issue #79340](https://github.com/microsoft/vscode/issues/79340) and submit PRs to help them out.
|
||||
|
||||
### Remote Development (Preview)
|
||||
|
||||
|
|
@ -277,7 +277,7 @@ To help get you started with the Remote Development extensions, there are three
|
|||
|
||||
We've published a repository of all of the [VS Code icons](https://github.com/microsoft/vscode-icons) for use by extension authors. There are dark/light versions of each icon, and we also linked to our [Figma design file](https://www.figma.com/file/7wJdjbq2rKZffZqPdz6OjN/VS-Code-Icons-%E2%80%94-Public?node-id=0%3A1) if you're 😎.
|
||||
|
||||
|
||||
|
||||
|
||||
### Webview.asWebviewUri and Webview.cspSource
|
||||
|
||||
|
|
@ -313,13 +313,13 @@ panel.html = `<!DOCTYPE html>
|
|||
</html>`
|
||||
```
|
||||
|
||||
### Development warning when creating webview that don't have a content security policy
|
||||
### Warning when creating webview without a content security policy
|
||||
|
||||
While developing an extension that uses the [Webview API](https://code.visualstudio.com/api/extension-guides/webview), we now log a warning when you create a webview that does not set a [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP).
|
||||
While developing an extension that uses the [Webview API](https://code.visualstudio.com/api/extension-guides/webview), we now log a warning when you create a webview that does not set a [Content Security Policy](https://developer.mozilla.org/docs/Web/HTTP/CSP).
|
||||
|
||||
|
||||
|
||||
All webviews (even very simple ones) should set a content security policy. This helps limit the potential impact of content injections and is generally a good measure for defense in depth. We've documented how to add a content security policy to VS Code webviews [here](https://code.visualstudio.com/api/extension-guides/webview#content-security-policy).
|
||||
All webviews (even very simple ones) should set a content security policy. This helps limit the potential impact of content injections and is generally a good measure for defense in depth. We've documented how to add a content security policy to VS Code webviews in the [Webview extension guide](https://code.visualstudio.com/api/extension-guides/webview#content-security-policy).
|
||||
|
||||
### Machine-specific overridable settings
|
||||
|
||||
|
|
@ -348,22 +348,22 @@ Trees contributed through `createTreeView` can now add the `canSelectMany` optio
|
|||
|
||||
### markdown.api.render
|
||||
|
||||
The new `markdown.api.render` command from VS Code's builtin markdown extension takes a `string` of markdown or a `vscode.TextDocument` and returns the rendered markdown as html:
|
||||
The new `markdown.api.render` command from VS Code's builtin Markdown extension takes a `string` of Markdown or a `vscode.TextDocument` and returns the rendered Markdown as HTML:
|
||||
|
||||
```ts
|
||||
import * as vscode from 'vscode';
|
||||
|
||||
export function activate(context: vscode.ExtensionContext) {
|
||||
vscode.commands.executeCommand('markdown.api.render', '# Hello markdown').then(result => {
|
||||
console.log(`rendered markdown: ${result}`);
|
||||
});
|
||||
vscode.commands.executeCommand('markdown.api.render', '# Hello Markdown').then(result => {
|
||||
console.log(`rendered markdown: ${result}`);
|
||||
});
|
||||
}
|
||||
```
|
||||
|
||||
Logs:
|
||||
|
||||
```html
|
||||
<h1 id="hello-markdown" data-line="0" class="code-line">Hello markdown</h1>
|
||||
<h1 id="hello-markdown" data-line="0" class="code-line">Hello Markdown</h1>
|
||||
```
|
||||
|
||||
## Language Server Protocol
|
||||
|
|
@ -380,7 +380,7 @@ In addition, we've added an optional `sortText` attribute to the `CompletionItem
|
|||
|
||||
### Fixed a type issue in DAP's JSON schema
|
||||
|
||||
In the [JSON schema](https://github.com/microsoft/debug-adapter-protocol/blob/gh-pages/debugAdapterProtocol.json) of the Debug Adapter Protocol, we've changed the use of the type specifier `number` to `integer` in those places where a float type makes no sense, for example for IDs.
|
||||
In the [Debug Adapter Protocol JSON schema](https://github.com/microsoft/debug-adapter-protocol/blob/gh-pages/debugAdapterProtocol.json), we've changed the use of the type specifier `number` to `integer` in those places where a float type makes no sense, for example for IDs.
|
||||
|
||||
## Proposed extension APIs
|
||||
|
||||
|
|
@ -392,7 +392,7 @@ Every milestone comes with new proposed APIs and extension authors can try them
|
|||
|
||||
Note that you cannot publish an extension that uses a proposed API. We may likely make breaking changes in the next release and we never want to break existing extensions.
|
||||
|
||||
### Deprecation-tags for symbols and completions
|
||||
### Deprecation tags for symbols and completions
|
||||
|
||||
The API for completions and document/workspace symbols now supports marking items as deprecated. Completions and symbols have a new, optional property `tags` that is a set of `CompletionItemTag`s or `SymbolTag`s. Today, only deprecation is supported but there plans to add more tags, for example tags for access modifiers and other modifiers.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,74 +2,74 @@
|
|||
|
||||
## VS Code Remote Core
|
||||
|
||||
### Install an Extension from VSIX from Remote Machine
|
||||
### Install an extension from VSIX from remote machine
|
||||
|
||||
You can now install an extension from VSIX that is located in the remote machine.
|
||||
You can now install an extension from a packaged VSIX that is located in the remote machine.
|
||||
|
||||
### Remote Explorer
|
||||
|
||||
We generalized the SSH Explorer and moved it into VS Code core as Remote Explorer. Remote extensions can contribute available remote targets, connection details and help information into the Remote Explorer. Remote Explorer will group and sort the views based on the sections they are contributing to.
|
||||
We generalized the SSH Explorer and moved it into VS Code core as the Remote Explorer. Remote extensions can contribute available remote targets, connection details, and help information into the Remote Explorer. The Remote Explorer will group and sort the views based on the sections they are contributing to.
|
||||
|
||||
### Reconnect Now
|
||||
### Reconnect Now command
|
||||
|
||||
Previously, if you were disconnected from a remote session for some reason, you had to wait for a timer to countdown before reconnection would occur. Now, you may simply click `Reconnect Now` to get right back to work.
|
||||
Previously, if you were disconnected from a remote session for some reason, you had to wait for a timer to count down before reconnection would occur. Now, you can run the **Reconnect Now** action to get right back to work.
|
||||
|
||||
## WSL
|
||||
|
||||
### Alpine WSL
|
||||
|
||||
Alpine WSL is now also enabled with VS Code stable builds. It is still in preview mode as extensions installed in Alpine Linux may not work due to glibc dependencies in native code inside the extension.
|
||||
Alpine WSL is now also enabled for VS Code Stable builds. Alpine support is still in preview mode as some extensions installed in Alpine Linux may not work due to glibc dependencies in native code inside the extension.
|
||||
|
||||
## Containers
|
||||
|
||||
### Alpine Linux
|
||||
|
||||
Support for Alpine Linux is now also enabled with VS Code stable builds. It is still in preview mode as extensions installed in Alpine Linux may not work due to glibc dependencies in native code inside the extension.
|
||||
Support for containers using Alpine Linux is now enabled for VS Code Stable builds. Alpine support is still in preview mode as some extensions installed in Alpine Linux may not work due to glibc dependencies in native code inside the extension.
|
||||
|
||||
Note that there is a [known issue](https://github.com/microsoft/vscode-remote-release/issues/1026) with Alpine 3.10 for which we remove logging through the `spdlog` library as a workaround while we continue to investigate.
|
||||
Note that there is a [known issue](https://github.com/microsoft/vscode-remote-release/issues/1026) with Alpine 3.10 and we removed logging through the `spdlog` library as a workaround while we continue to investigate.
|
||||
|
||||
### Multi-Folder Workspace Support
|
||||
### Multi-folder workspace support
|
||||
|
||||
We have added support for multi-folder workspaces. You can reopen an already open workspace in a container and pick a container definition to start from.
|
||||
There is now support for multi-folder workspaces. You can reopen an already open workspace in a container and pick a container definition to start from.
|
||||
|
||||
Currently all folders must have the folder with the `.workspace` file as their parent folder and they must be referenced in the `.workspace` file using relative paths.
|
||||
|
||||
### Mount Consistency
|
||||
### Mount consistency
|
||||
|
||||
The consistency for the default mount point is now `cached` which should improve file performance on OSX. This can be configured with the Workspace Mount Consistency setting.
|
||||
The consistency for the default mount point is now `cached`, which should improve file performance on macOS. This can be configured with the Workspace Mount Consistency setting.
|
||||
|
||||
.
|
||||
|
||||
### Variable for Local Workspace Folder
|
||||
### Variable for local workspace folder
|
||||
|
||||
In the `devcontainer.json` there is a new variable `${localWorkspaceFolder}` for the local folder's path.
|
||||
In the `devcontainer.json`, there is a new variable `${localWorkspaceFolder}` for the local folder's path.
|
||||
|
||||
### Guidance for Existing Dockerfile / docker-compose.yml
|
||||
### Guidance for existing Dockerfile / docker-compose.yml
|
||||
|
||||
When creating the `devcontainer.json` from an existing `Dockerfile` or `docker-compose.yml` we now use a full-fledged definition from the [vscode-dev-containers](https://github.com/microsoft/vscode-dev-containers) providing additional guidance in the `devcontainer.json` with comments and examples of configuration options.
|
||||
When creating the `devcontainer.json` from an existing `Dockerfile` or `docker-compose.yml`, we now use a full-fledged definition from the [vscode-dev-containers](https://github.com/microsoft/vscode-dev-containers), providing additional guidance in the `devcontainer.json` with comments and examples of configuration options.
|
||||
|
||||
### List of Service to Start / Stop
|
||||
### List of service to start / stop
|
||||
|
||||
When using Docker Compose there is now a configuration option `"runServices"` in the `devcontainer.json` for choosing which services should be started and stopped when opening / closing the DevContainer using Compose. The default remains to start and stop all services. The `"shutdownAction"` can be used to override what happens during shutdown.
|
||||
When using Docker Compose, there is now a configuration option `"runServices"` in the `devcontainer.json` for choosing which services should be started and stopped when opening / closing the DevContainer using Compose. The default remains to start and stop all services. The `"shutdownAction"` can be used to override what happens during shutdown.
|
||||
|
||||
### Explorer
|
||||
|
||||
Containers had been added to the new Remote Explorer. You can see and manage your containers from the Targets (Containers) view and when you're connected to a container you can see more information about it in the Details (Containers) view. From the Targets view you can open dev container folders, attach to containers, and start/stop/remove containers. From the Details view you can forward ports and open the ports you have forwarded in a browser.
|
||||
Containers had been added to the new Remote Explorer. You can see and manage your containers from the **Targets (Containers)** view and when you're connected to a container you can see more information about it in the **Details (Containers)** view. From the Targets view, you can open dev container folders, attach to containers, and start/stop/remove containers. From the Details view, you can forward ports and open the ports you have forwarded in a browser.
|
||||
|
||||
|
||||
|
||||
## SSH
|
||||
|
||||
### ARMv7l Support in Stable
|
||||
### ARMv7l support in Stable
|
||||
|
||||
A couple months ago, we added experimental support for ARMv7l 32-bit when using VS Code Insiders. With 1.38 this is now supported in stable VS Code as well. This means you can now connect to a Raspberry Pi 2/3 via SSH and edit files using stable VS Code.
|
||||
A couple months ago, we added experimental support for ARMv7l 32-bit when using VS Code Insiders. With 1.38, this is now supported in Stable VS Code as well. This means you can now connect to a Raspberry Pi 2/3 via SSH and edit files using Stable VS Code.
|
||||
|
||||
### Experimental ARMv8l (AArch64) Linux support
|
||||
|
||||
Experimental support for ARMv8l (AArch64) is now available when using [VS Code Insiders](https://code.visualstudio.com/insiders/) only.
|
||||
|
||||
We are holding this back from the stable release to allow for extension authors to catch up with the additional platform, see [Supporting Remote Development](https://code.visualstudio.com/api/advanced-topics/remote-extensions) for details.
|
||||
We are holding this back from the Stable release to allow for extension authors to catch up with the additional platform, see [Supporting Remote Development](https://code.visualstudio.com/api/advanced-topics/remote-extensions) for details.
|
||||
|
||||
### Experimental features turned on by default
|
||||
|
||||
Last month we added experimental support for SSH's `ForwardAgent` option, and "dynamic forwarding" which provides a better experience when using password auth. Those features are now enabled for everyone by default.
|
||||
Last month we added experimental support for SSH's `ForwardAgent` option and "dynamic forwarding", which provides a better experience when using password auth. Those features are now enabled by default.
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче