From a1a724ae28f6b66224061283c853423489a1cbdc Mon Sep 17 00:00:00 2001 From: Andre Weinand Date: Mon, 28 Feb 2022 12:54:27 +0100 Subject: [PATCH] add two DAP items --- release-notes/v1_65.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/release-notes/v1_65.md b/release-notes/v1_65.md index 61dc50229..2b9855d55 100644 --- a/release-notes/v1_65.md +++ b/release-notes/v1_65.md @@ -376,6 +376,11 @@ Another nexte version of the [Language Server Protocol](https://microsoft.github - the conversion of LSP types into VS Code types and vice versa is now fully async. This avoid that the conversion of large data streams can block the extension host. Please note that this is a breaking API change in the libraries (see also the [readme.md](https://github.com/microsoft/vscode-languageserver-node/blob/081ba82a0e49eebec2d1b7d93751290cc1128104/README.md#L47)). It does not affect the backwards compatibility of the protocol itself. - the proposed implementation for notebook documents got enhanced. It has now full middleware and provider support. +## Debug Adapter Protocol + +- A new boolean property `lazy` has been added to the `VariablePresentationHint`. Clients can use the optional flag to present the variable with a UI that supports a specific gesture to fetch its value. +- A new optional string property `detail` has been added to the `CompletionItem`. With this human-readable string a client can show additional information about the item, like type or symbol information. Please note that this property is not yet supported by VS Code. + ## Proposed extension APIs Every milestone comes with new proposed APIs and extension authors can try them out. As always, we want your feedback. Here are the steps to try out a proposed API: