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

42 KiB
Исходник Ответственный История

Order TOCTitle PageTitle MetaDescription MetaSocialImage Date DownloadVersion
48 September 2019 Visual Studio Code September 2019 See what is new in the Visual Studio Code September 2019 Release (1.39) 1_39/release-highlights.png 2019-10-09 1.39.2

September 2019 (version 1.39)

Update 1.39.1: The update addresses these issues, including a fix for a security vulnerability.

Update 1.39.2: The update addresses these issues.

Welcome to the September 2019 release of Visual Studio Code. There are a number of updates in this version that we hope you will like, some of the key highlights include:

If you'd like to read these release notes online, go to Updates on code.visualstudio.com.

Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. And for the latest Visual Studio Code news, updates, and content, follow us on Twitter @code!

Workbench

Updated Source Control view

The Source Control view has been updated to use the latest tree widget. You can now toggle between a list and a tree view with the Toggle View Mode button on the Source Control title bar.

Source Control toggle view mode button

You can change the default view using the scm.defaultViewMode setting, which takes the values list or tree.

You also now benefit from the automatic keyboard navigation and filtering of the updated tree widget by simply starting to type in the view.

Updated SCM view

When in tree view mode, which displays folders, the Git extension now contributes commands to folders, for example Stage Changes, which will be applied to all files within a folder.

Improved Trusted Domains setting

We simplified the management of trusted domains for the outgoing link protection feature introduced in the 1.38 release.

You can now use the command Manage Trusted Domains to easily add, remove, or modify trusted domains as a JSON text file.

Improved trusted domains management

Selectable completion details

Auto completion details can now be selected for copy and paste.

Selectable completion details

Updated Japanese UI font on Windows

On Windows, we have switched the Japanese UI typeface from Meiryo to Yu Gothic UI and Meiryo UI.

The UI typefaces save horizontal space by using narrower Japanese kana characters. You can use the Japanese UI by installing the Japanese Language Pack and, with the Configure Display Language command, setting the display language identifier to ja.

In the image below, you can see how the narrower UI typeface looks in the Insiders (green icon) menu bar.

Japanese typeface

Improved monospace typeface display in suggestions and hovers

Previously, the inline <code> segments in the suggestion and hover widgets didn't specify font-family. On Windows / macOS, these segments were rendered with Chrome's default choice for font-family: monospace.

In this iteration, we aligned them with the system sans-serif typefaces that are used throughout the VS Code UI.

  • Windows: Courier New -> Consolas (To align with Segoe UI)
  • macOS: Courier -> SF Mono, Monaco, Menlo (To align with SF Text and Helvetica Neue)
  • Linux: No change. Inline code segments still rendered in Liberation Mono, which is Chrome's default for font-family: monospace on Linux.

Below you can see that SF Mono gives a more consistent appearance to the inline code blocks.

Suggest and Hover widgets monospace typeface

Validation for uniqueItems in the Settings editor

Validation for string array settings, which was introduced in the 1.38 release, now supports uniqueItems.

If using "uniqueItems": true, duplicate entries in the Settings editor will show a warning.

Code block highlighting in extension READMEs

Code blocks in extension READMEs, which are displayed in the Extensions view Details pane, are now highlighted in VS Code:

A block of JSON being highlighted

The highlighting uses the current color theme.

Editor

Toggle folding

You can now expand and collapse a folding region with the Toggle Fold (kb(editor.toggleFold)) command.

Minimap editor selection decorations

The editor selection is now highlighted within the minimap:

Minimap displays the editor selection

You can change the color of these decorations by modifying the minimap.selectionHighlight theme color.

Touch events for the minimap

The minimap slider can now be dragged with touch.

New option for multi cursor pasting

In the past, when pasting multi-line text from the clipboard, VS Code would check if the clipboard text line count matched the cursor count, and if it did, it would "distribute" or "spread" each line to a cursor. You can now control this behavior with the editor.multiCursorPaste setting, which can have the values:

  • spread - Each cursor pastes a line of text (default).
  • full - Each cursor pastes the full clipboard text.

Integrated Terminal

Open new terminals with custom working directories

There is a new command that allows the creation of terminals with a custom current working directory (cwd):

{
  "key": "cmd+shift+h",
  "command": "workbench.action.terminal.newWithCwd",
  "args": {
    "cwd": "${fileDirname}"
  }
}

You can create your own keyboard shortcuts to open new terminals in any number of handy working directories. The cwd value can either be a normal path or a variable.

Better locale detection

The terminal.integrated.setLocaleVariables setting has been replaced with the new terminal.integrated.detectLocale setting. The default value is auto, which will set the $LANG variable in your terminal session to the detected language UTF-8 value but only when it has not been explicitly configured by the user. This better default should lead to fewer issues related to language and encoding in the terminal.

Languages

HTML ARIA attributes reference

Auto completion and hover information for HTML ARIA attributes now include a reference to the corresponding WAI-ARIA documentation.

HTML ARIA reference

CSS property completion with semicolon

CSS property completion now inserts a semicolon at the end of a line.

You can use this feature with kbstyle(Ctrl+Enter) (Windows / Linux) or kbstyle(Cmd+Enter) (macOS) to create a new line without pushing the ending ; to the new line.

You can control this feature with the [css|scss|less].completion.completePropertyWithSemicolon settings.

CSS property completion semicolon

CSS color preview for variable completion

When completing CSS variables, if the original variable is a color string, VS Code now shows the completion item with its color:

CSS variable completion with color swatch

markdown.links.openLocation

The new markdown.links.openLocation setting controls where links within Markdown files are opened.

markdown.links.openLocation has two values:

  • currentGroup - Opens links in the current editor group (default).
  • beside - Open links to the side of the current Markdown editor.

"markdown.links.openLocation": "beside" can be useful when working on documentation.

Debugging

Improved UI for column breakpoints

While debugging, VS Code now shows all the breakpoint candidate locations inline. This makes it easier for the user to place a breakpoint on a more accurate position. To not clutter the UI, candidate breakpoints are only shown if there is more than one possible location on the line.

You can interact directly with inline breakpoints; clicking to enable and disable them and invoking their context menu for more actions.

Inline breakpoints

Note that this feature requires support by the underlying runtime or debugger, and we expect only a few debug extensions will use this feature in the future. For this release, Node Debug and the Debugger for Chrome support this. As an example for extension authors, our Mock Debug sample "mocks" support for this.

Inline debug actions in CALL STACK view

When there are sessions or threads shown in the CALL STACK view, we now show debug actions inline on hover. This will make it easier to control the debug flow when debugging multiple sessions or threads. You no longer need to first set focus on a session or thread in order to perform an action on it.

If a session has only one thread, all actions are shown on the session since the thread is not displayed. Otherwise all actions are shown in their context (session actions on sessions and thread actions on threads).

Inline debug actions from the Call Stack view

Improved CALL STACK view behavior

We improved the functionality of the CALL STACK view:

  • Clicking on the debug session or the thread no longer expands them. You have to click on the chevron (>) UI element directly. This prevents accidentally expanding a session or thread when you just want to move focus.
  • VS Code no longer automatically focuses new debug sessions if they did not break.

Improved link detection in Debug Console

VS Code now detects links in expressions in the Debug Console, not only in string output. The link detection algorithm was also improved.

PreLaunchTask can now refer to default build

With the introduction of a new variable ${defaultBuildTask}, it is now possible to have a generic preLaunchTask that always refers to the default build task:

{
    "name": "Hello World",
    "type": "node",
    "request": "launch",
    "preLaunchTask": "${defaultBuildTask}"
}

${defaultBuildTask} resolves to the name of the task that is run when the command Tasks: Run Build Task is executed. Similar to using the Run Build Task command, if there are multiple default build tasks, or no default build task, then a Quick Pick is shown to select the build task.

Save choice when preLaunchTask errors

You can now remember your choice when there is a preLaunchTask error with the Remember my choice in user settings checkbox. Your choice is stored in user settings with debug.onTaskErrors, which can have three values; prompt (default), debugAnyway, and showErrors.

PreLaunchTask error choice dialog

Contributions to extensions

Remote Development (Preview)

Work has continued 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.39 include:

  • Remote Explorer now supports the Remote - WSL extension and lets you easily connect to installed Linux distros.
  • New Open Repository in Container command so you can work on source code repositories in isolation.
  • Experimental support for SSH connection sharing and using SSH to connect to Windows remote machines.

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

You can also read two recent blog posts describing:

Preview features

Preview features are not ready for release but are functional enough to use. We welcome your early feedback while they are under development.

TypeScript 3.7-beta support

Although VS Code will not bundle TypeScript 3.7 until its official release, we have already been working to support all the exciting new TypeScript 3.7-beta features.

These include:

  • Syntax highlighting of optional chaining and nullish coalescing in JavaScript and TypeScript files.
  • Completion support for optional chaining.
  • Control over semicolons with the new javascript.format.semicolons and typescript.format.semicolons settings.

You can easily try all these new TypeScript 3.7 features today by installing the TypeScript Nightly extension. Please share feedback and let us know if you run into any bugs with the TypeScript 3.7 beta!

Extension authoring

Extension terminal API

The extension terminal API has been finalized, allowing an extension to react to terminal input and fully control its output. The following creates an extension terminal and prints 'Hello world' in red on startup:

const writeEmitter = new vscode.EventEmitter<string>();
const pty: vscode.Pseudoterminal = {
  onDidWrite: writeEmitter.event,
  open: () => writeEmitter.fire('\x1b[31mHello world\x1b[0m'),
  close: () => {}
};
vscode.window.createTerminal({ name: 'My terminal', pty });

See the API reference and the extension-terminal-sample for more details.

Deprecation tags for symbols and completions

The symbol tag API that allows completion items and symbols to be marked as deprecated has been finalized. Learn more about it in the 1.38 release notes.

Here you can see that the Java extension is using SymbolTag.Deprecated to show source code that references deprecated types or members with a strike-through line.

Java deprecated method

Debug Session name is no longer readonly

It is possible to change the name of the DebugSession. The debug session's name is initially taken from the DebugConfiguration. Any changes will be properly reflected in the UI.

Warning if webviews don't use Webview.asWebviewUri for local resources

While developing an extension that uses the Webview API, we now log a warning when you create a webview that loads local resources using vscode-resource: URIs directly instead of using the new Webview.asWebviewUri API.

Debug warning for a webview that uses vscode-resources

Although old vscode-resource: URIs will continue to work, we want all webview extensions to migrate to the Webview.asWebviewUri API as the new API:

  • Handles some tricky edge cases around loading local resources from network drives.
  • Makes it possible to have a webview that can load a mix of local and remote content.
  • Will work more reliably for web versions of VS Code.

TreeView message API

The API to set a message in a tree view has been finalized. You can see an example of how to use the message API in the tree view extension sample.

Updated Octicons style

We've updated our Octicons to match our new icon outline style so that all of our iconography is consistent.

Updated Octicons

SCM folder menu

The updated SCM view now supports rendering changes as a tree. As an SCM provider, you can contribute commands to a folder's menu using the scm/resourceFolder/context menu id.

Language Server Protocol

The specification of the 3.15.0 version of the Language Server Protocol is available. The version is not final yet so feedback is still welcome as an issue or a pull request in the Language Server Protocol repository. Streaming and progress reporting support has been added to the next version of the language server protocol. Implementations for the node server and the VS Code client are available as vscode-languageserver@6.0.0-next.1 and vscode-languageclient@6.0.0-next.1 respectively.

Debug Adapter Protocol

Cancellation support

A new cancel request has been added to the Debug Adapter Protocol that can give a hint to the debug adapter that the frontend client is no longer interested in the result produced for a specific request issued earlier.

This request has a hint characteristic: a debug adapter can only be expected to make a 'best effort' in honoring this request but there are no guarantees. A frontend client may only call this request if the capability supportsCancelRequest is defined and has the value of true.

The request that was canceled still needs to send a response back. This can either be a normal result or an error response. Returning partial results from a canceled request is possible but note that a frontend client has no generic way for detecting that a response is partial or not.

In the September release, VS Code supports cancellation for the stacktrace, scopes, and variables requests (used in the CALL STACK and VARIABLES views) and the completions requests (used in the Debug Console).

Note that as of September, only the Mock Debug extension implements cancellation.

Finding possible breakpoints in a source range

The new breakpointLocations request can be used by a DAP client to find all possible breakpoint locations in a given source range. This can be used in the UI in order to improve the discoverability of "inline" ("column") breakpoints.

A client may only call the breakpointLocations request if the supportsBreakpointLocationsRequest capability is defined and has the value of true.

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 file into your project's source location.

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.env.uiKind

A new proposed API vscode.env.uiKind was added that allows an extension to figure out from what kind of UI the extension is being used from. In preparation for supporting running VS Code in a browser, the possible values are UIKind.Desktop and UIKind.Web.

vscode.env.asExternalUri

The proposed vscode.env.asExternalUri API allows an extension to resolve an external URI - such as a http: or https: URI - from where the extension is running to a URI for the same resource on the client machine. This is a companion to the vscode.env.openExternal API, except instead of opening the resolved URI using an external program, it returns the result to extensions.

import * as vscode from 'vscode';
import * as http from 'http';

const PORT = 3000;

export function activate(context: vscode.ExtensionContext) {
  startLocalServer(PORT);

  context.subscriptions.push(vscode.commands.registerCommand('example.command', async () => {
      const resolved = vscode.env.asExternalUri(vscode.Uri.parse(`http://localhost:${PORT}`));
      vscode.window.showInformationMessage(`Resolved to: ${resolved} on client and copied to clipboard`);
      vscode.env.clipboard.writeText(resolved.toString());
  }));
}

function startLocalServer(port: number) {
  const server = http.createServer((req, res) => {
    res.end('Hello world!');
  });
  server.on('clientError', (err, socket) => {
    socket.end('HTTP/1.1 400 Bad Request\r\n\r\n');
  });
  server.listen(port);
  vscode.window.showInformationMessage(`Started local server on port: ${port}`);
}

vscode.env.asExternalUri currently only supports http: and https: URIs. It is a no-op if the extension is running on the client machine. However, if the extension is running remotely, vscode.env.asExternalUri automatically establishes a port forwarding tunnel from the local machine to target on the remote and returns a local URI to the tunnel.

Readonly webview editors for resources

You can find VS Code extensions for previewing everything from shaders to Excel files to 3D models. A few bold extensions have even built complex editor-style experiences for visually editing binary or XML files. While it's great that all this is already possible using VS Code's existing extension API, building a preview or custom editor currently requires cobbling together a bunch of APIs in non-intuitive ways. It also leaves a lot up to extensions themselves, often resulting in user experiences that are not consistent with the rest of VS Code. The custom editor API proposal aims to improve this.

The custom editor API will provide a framework for extensions to create fully customizable read/write editors that are used in place of VS Code's standard text editor for specific resources. A XAML custom editor, for example, could show a WYSIWYG style editor for your .xaml files. Our end goal is to give extensions the most flexibility possible while keeping VS Code fast, lean, and consistent.

This iteration, we are sharing the first pieces of the custom editor API proposal: readonly, webview-based custom editors. You can find an overview of the custom editor proposal here. Custom editors are already being used to power VS Code's built-in image preview.

The current proposal is only a first step and will likely be heavily revised. We will continue to iterate on the custom editor API over the coming months.

TreeView title

The tree view title has always been taken from the extension's package.json file. Now, a tree view title is initially taken from package.json but can be changed later. Changes to the title property will be properly reflected in the UI in the title of the view.

startDebugging consoleMode option to merge Debug Consoles

In order to support hierarchical debug sessions better, we've added an optional argument consoleMode to the vscode.debug.startDebugging API. This argument controls if VS Code should merge the Debug Console of the parent and child debug sessions. For example, this is particularly useful for cluster debugging, where there are many child sessions and it is much cleaner if all the debug sessions go to the same Debug Console.

Removed deprecated Terminal.onDidWriteData API

The Terminal.onDidWriteData proposed API has been removed in favor of the global event window.onDidWriteTerminalData.

Engineering

Website refresh

We updated the Visual Studio Code website icons and colors to better match our brand. This is reflected throughout the website and documentation pages.

Website colors updated

JavaScript minification via terser

We changed the minifier used for minification of JavaScript for the product build to be terser. Previously we had been using an older version of uglify-es. The terser developers have been very helpful supporting us during the adoption.

Filewatcher update (Chokidar)

During this milestone, we updated our file watcher for macOS and Linux to version 3.x, which brings improved performance, reduced memory consumption, and a smaller package size. You can learn more from the Chokidar repo and Chokidar 3 blog post.

Integration tests run against the real build

Our product builds run a large integration test suite as part of the build. Previously, these tests were executing against VS Code running out of sources. Now, these tests use the built version of VS Code to verify that the build is ready to be released.

Building VS Code using TypeScript 3.6

VS Code core and the built-in extensions are now built using TypeScript 3.6.

Image preview moved to a built-in extension

VS Code's image preview functionality has been moved out of the core codebase and into a built-in Image Preview extension. The functionality of image previews should be almost exactly the same as before.

The built-in Image Preview extension

Extracting image preview into a built-in extension makes it easier to fix bugs and add features, and will eventually allow extensions to override VS Code's built-in image preview more easily.

This change was enabled by the custom editor API work we completed this iteration.

New documentation

Node.js deployment tutorials

The Node.js deployment tutorials have moved to the Azure JavaScript Developer Center on docs.microsoft.com.

There you can find tutorials for using Visual Studio Code to:

Notable fixes

  • 78984: Touch doesn't work in Suggest widget
  • 79196: debug console shows REPL results and console.log output in wrong order
  • 80003: Regular breakpoints don't have a title tooltip
  • 55106: Breakpoints appear as verified if verified by at least one session
  • 80435: Please let me hide the empty folder section in the explorer sidebar
  • 80464: Failure message from SetVariable request is not surfaced
  • 80402: debug UI doesn't cleanup spinners on debug session end
  • 82047: New title variable to indicate the remote name

Thank you

Last but certainly not least, a big Thank You! to the following folks that helped to make VS Code even better:

Contributions to our issue tracking:

Please see our Community Issue Tracking page, if you want to help us manage incoming issues.

Contributions to vscode:

Contributions to vscode-eslint:

Contributions to vscode-languageserver-node:

Contributions to language-server-protocol:

Contributions to debug-adapter-protocol:

Contributions to vscode-debugadapter-node:

Contributions to vscode-css-languageservice:

Contributions to vscode-vsce:

Contributions to localization:

There are over 800 Cloud + AI Localization community members using the Microsoft Localization Community Platform (MLCP), with over about 100 active contributors to Visual Studio Code. We appreciate your contributions, either by providing new translations, voting on translations, or suggesting process improvements.

Here is a snapshot of contributors. For details about the project including the contributor name list, visit the project site at https://aka.ms/vscodeloc.

  • Danish: Mark Drastrup, Lasse Stilvang.
  • Dutch: Niels ter Haar, Laurens Kwanten.
  • English (United Kingdom): Martin Littlecott, s.benson, sonali Dixit.
  • Finnish: Kiti Suupohja, Tommi Finnilä.
  • French: Thierry DEMAN-BARCELÒ, Maxime Coquerel, Antoine Griffard, Rodolphe NOEL, DJ Dakta.
  • German: Christof Opresnik.
  • Greek: Θοδωρής Τσιρπάνης.
  • Hebrew: Yonatan Bachar, Snir Broshi.
  • Hindi: mtar05, निरव आडतिया, Amit Gusain, Degant Puri.
  • Chinese Simplified: Justin Liu, Yizhi Gu, paul cheung, yungkei fan, 斌 项, Yiting Zhu, 一斤瓜子, Tianzhi Zeng, cool yang, Peng Zeng, Y!an, Joel Yang, 楠 姜, 建 周.
  • Chinese Traditional: Winnie Lin, 蔡牧村, 謝政廷, Yi-Jyun Pan, Poy Chang.
  • Indonesian: Eriawan Kusumawardhono, Riwut Libinuko, William Surya Permana, Septian Adi, Laurensius Dede Suhardiman.
  • Italian: Luigi Bruno, Alessandro Alpi, Claudio Mezzasalma, Marco Dal Pino.
  • Japanese: Michihito Kumamoto, Hiroyuki Mori, Aya Tokura, 井上 圭司, Yuzo Konishi, Yoshihisa Ozaki, Kogesaka, Yuta Ojima, TENMYO Masakazu, Koichi Makino, Takayuki Fuwa.
  • Korean: Hongju, Sungjin Jeong, Seikwang Chung.
  • Latvian: Andris Vilde.
  • Lithuanian: Renatas Laužadis.
  • Polish: Kacper Łakomski.
  • Portuguese (Brazil): Marcelo Fernandes, Marcondes Alexandre, Felipe Oliveira, Alan Bueno.
  • Portuguese(Portugal): Pedro G..
  • Romanian: Mihail-Gabriel Alexe.
  • Russian: konpl.
  • Spanish: José María Aguilar, Abdón Rodríguez P., Ricardo Estrada Rdez, Anix Cormak, Carlos Mendible.
  • Tamil: Rajeshkumar Ramasamy.
  • Turkish: Safa Selim.
  • Ukrainian: Oleksandr Krasnokutskyi, Arthur Murauskas.
  • Vietnamese: Vương, Van-Tien Hoang, Hai Nguyen, Tuan Duong.