This commit is contained in:
Greg Van Liew 2019-08-01 17:11:50 -07:00
Родитель 9de039d4d6
Коммит ce5e02764b
5 изменённых файлов: 59 добавлений и 32 удалений

Просмотреть файл

@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:34ea66b8553d02407ffcd702457c3639dc2dd9c32c13f0da87c8c8820c4cb5f6
size 74519
oid sha256:f7f02a1cfabb425ca7856c61b363533857468de14be2a0e1bc8f68896f0a594d
size 54071

Просмотреть файл

@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:3d0a78b406a942ce3360b9da63803308e8d8a31af7b6fb0d39b47db4efbcc042
size 103752
oid sha256:2e1cbe8b05e980efaf112a51c9222ceee4a31fe4d501f2e59b256e5ee59dad96
size 89476

Просмотреть файл

@ -33,6 +33,7 @@ The `editor.renderWhitespace` setting now supports a `selection` option. With th
![Whitespace rendered on selection](images/1_37/render-whitespace-on-selection.png)
This is handy for quickly checking whitespace without filling the entire editor.
### Settings editor support for array-of-string settings
@ -51,13 +52,13 @@ Extension authors can enable this support by [contributing a configuration](http
}
```
### Removed warnings from Settings files
### Removed warnings from settings files
Settings files will not show warnings for unknown or unsupported settings now. Warnings are also not shown when you have configured settings from extensions which are disabled. Instead these are shown as unused code.
You will no longer see warnings for unknown or unsupported settings in your `settings.json` files. Instead inactive settings will be dimmed, similar to unused source code. In addition, you won't see warnings for settings from extensions that are disabled.
![Unused Settings](images/1_37/unused-settings.png)
### Improved minimap search decoration visibility
### Improved minimap search results visibility
In the previous release, we introduced search decorations in the minimap. These decorations were difficult to see, so this iteration, we've worked on increasing their visibility. Now, the entire line will now be highlighted with low opacity in the minimap, and the actual match shown with high opacity.
@ -65,9 +66,9 @@ In the previous release, we introduced search decorations in the minimap. These
You can also change the color of the decorations using the new `minimap.findMatchHighlight` theme color.
### `focusedView` context key
### focusedView context key
Introduced a new context key `focusedView` which can be used to define keybinding when a given view is focused
There is a new keybinding `when` context key `focusedView` to display or enable a keybinding when a given view is focused.
`"when": "focusedView == nodeDependencies"`
@ -85,13 +86,21 @@ VS Code used to resolve SCSS imports statically. For example, `@import './foo'`
VS Code now resolves `@import './foo'` to one of these locations if the resolved file exists on disk. Note that if a link ends with `/`, it will only resolve to either `/index.scss` or `/_index.scss`. If a link ends with suffix such as `.css` or `.scss`, VS Code will not try the alternative file locations.
## Contributions to extensions
### Remote Development (Preview)
Work has continued on the [Remote Development](https://aka.ms/vscode-remote/download/extension) extensions, which allow you to use a container, remote machine, or the [Windows Subsystem for Linux](https://docs.microsoft.com/windows/wsl) (WSL) as a full-featured development environment. You can learn about new extension features and bug fixes in the [Remote Development release notes](https://github.com/microsoft/vscode-docs/tree/master/remote-release-notes/v1_37.md).
You can also read two recent blog posts describing [Linux development with WSL and Visual Studio Code](https://devblogs.microsoft.com/commandline/an-in-depth-tutorial-on-linux-development-on-windows-with-wsl-and-visual-studio-code) and [Remote development over SSH](https://code.visualstudio.com/blogs/2019/07/25/remote-ssh).
## Extension authoring
### vscode.workspace.fs
There is new API that allows to read, write, and manage files and folders. This is an alternative to Node.js's [fs](https://nodejs.org/dist/latest-v10.x/docs/api/fs.html)-module and more important it allows to access files from contributed file systems, like the ssh or wsl remote file systems.
There is new API for extensions to read, write, and manage files and folders. This is an alternative to Node.js's [fs](https://nodejs.org/dist/latest-v10.x/docs/api/fs.html) module and more importantly, it allows access to files from contributed file systems, such as the SSH or WSL remote file systems.
The snippet below shows how to write to a file, more usage samples can be found here: https://github.com/microsoft/vscode-extension-samples/tree/0b3a31bf2bdd388ac4fdc0ccea2fb1315abfe3e3/fsconsumer-sample.
The snippet below shows how to write to a file, more usage samples can be found in the [fsconsumer-sample](https://github.com/microsoft/vscode-extension-samples/tree/0b3a31bf2bdd388ac4fdc0ccea2fb1315abfe3e3/fsconsumer-sample).
```ts
const writeStr = '1€ is 1.12$ is 0.9£';
@ -102,11 +111,11 @@ await vscode.workspace.fs.writeFile(someUri, writeBytes);
### DiagnosticsTag.Deprecated
Diagnostic tags enable extensions authors to enrich the representation of diagnostics inside the editor. This release adds `DiagnosticTag.Deprecated` and the editor will render such diagnostics with a strike through line.
Diagnostic tags enable extension authors to enrich the representation of diagnostics inside the editor. This release adds `DiagnosticTag.Deprecated`, which the editor will render with a strike-through line.
![Strikeout decoration](images/1_37/diag-tag-deprecated.png)
### vscode.workspace.workspaceFile moved to API
### vscode.workspace.workspaceFile
There is a new workspace property `workspace.workspaceFile` returning the location of the workspace file. For example: `file:///Users/name/Development/myProject.code-workspace` or `untitled:1555503116870` for a workspace that is untitled and not yet saved.
@ -127,9 +136,17 @@ One use of the workspace file location is to call the `vscode.openFolder` comman
## Proposed extension APIs
Every milestone comes with new proposed APIs and extension authors can try them out. As always we are keen on your feedback. This is what you have to do to try out a proposed API:
* You must use Insiders because proposed APIs change frequently.
* You must have this line in the `package.json` file of your extension: `"enableProposedApi": true`.
* Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) file into your project.
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.
### vscode.commands.onDidExecuteCommand
There is a new event that fires whenever an event has been executed - its payload identifies the command and arguments.
There is a new event that fires whenever a command has been executed and the event's payload identifies the command and arguments.
```ts
export interface CommandExecutionEvent {
@ -144,6 +161,15 @@ export namespace commands {
}
```
## New documentation
## Remote Development tutorials
There are new step-by-step tutorials to walk you through running Visual Studio Code with the Remote Development extensions.
* [Remote via SSH](/remote-tutorials/ssh/getting-started) - Connect to remote and virtual machines with Visual Studio Code via SSH.
* [Working in WSL](/remote-tutorials/wsl/getting-started) - Run Visual Studio Code in Windows Subsystem for Linux.
## Notable fixes
* [422](https://github.com/microsoft/vscode/issues/422): Preserve window size when restoring a maximized window
@ -158,7 +184,6 @@ Contributions to `language-server-protocol`:
* [Marcin Krzyzanowski (@krzyzanowskim)](https://github.com/krzyzanowskim): Typos fixes [PR #789](https://github.com/microsoft/language-server-protocol/pull/789)
Contributions to `vscode-generator-code`:
* [Tomáš Hübelbauer (@TomasHubelbauer)](https://github.com/TomasHubelbauer): Make this generator work with require.resolve [PR #179](https://github.com/microsoft/vscode-generator-code/pull/179)

Просмотреть файл

@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:3a98ff59fb43554b875e3018d915437782b522e2769cc28b9c29809daa81badf
size 300182
oid sha256:b7bfe5da3bd833632a47703b4cf33ff7718bfd497cbc4ab696a51770d2e38025
size 186295

Просмотреть файл

@ -4,40 +4,42 @@
### Empty remote window presentation
When an empty remote window is opened (no folder, no workspace file) and the startup editor is not the welcome page, we now show the projects view and the terminal.
Use the `Open` button from the explorer to select a remote folder, or use the terminal to open files and folders.
When an empty remote window is opened (no folder, no workspace file) and the startup editor is not the Welcome page, we now show the projects view and the terminal. Use the **Open** button from the explorer to select a remote folder, or use the terminal to open files and folders.
### Remote settings
Remote settings file now supports edit actions.
The Remote settings file now supports edit actions.
![Remote Settings](images/1_37/remote-settings.png).
### Install Local Extensions in Remote Server
A new action is introduced to remote window that will allow you to select and install local extensions in remote server.
There is a new command **Extensions: Install Local Extensions in** when running remotely to select and install local extensions in the remote server.
![Install Local Extensions](images/1_37/install-local-extensions-remote.gif).
## Containers
## WSL
### Experimental Alpine Linux support
The Remote WSL extension now also support the Alpine WSL distro.
- you need to be on Windows 10, May 2019 Update (1903)
- install `Alpine WSL` from the Microsoft Store
- install the latest Remote WSL extension in an [VSCode Insiders](https://code.visualstudio.com/insiders/) build.
(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)
The Remote - WSL extension now supports the Alpine WSL distribution on VS Code Insiders.
- The Remote WSL etension will ask you to install `libstdc++` inside Alpine. To do that, open a Alpine WSL shell and run `su -c 'apk update && apk add libstdc++'`.
- To bring up the WSL Remote Window:
- run `code-insiders .` from the WSL shell
or
- invoke the `Remote-WSL: New Window using Distro` command and pick `Alpine`
To use an Alpine distro:
- You need to be on Windows 10, May 2019 Update (1903).
- Install **Alpine WSL** from the Microsoft Store.
- Install the latest Remote - WSL extension in a [VS Code Insiders](https://code.visualstudio.com/insiders/) build.
- The Remote - WSL extension will prompt you to install `libstdc++` inside Alpine. To do that, open an Alpine WSL shell and run `su -c 'apk update && apk add libstdc++'`.
To bring up the Remote - WSL window (instance) either:
- Run `code-insiders .` from the WSL shell.
- Invoke the **Remote-WSL: New Window using Distro** command and pick **Alpine**.
![Alpine](images/1_37/alpine.png)
**Note**: We are holding this back from the Stable release to allow extension authors to catch up with the additional platform. See [Supporting Remote Development](https://code.visualstudio.com/api/advanced-topics/remote-extensions) for details.
## SSH