transfer characters from microsoft private character editor

Notification and requests whose methods start with ‘$/’ are messages which are protocol implementation dependent and might not be implementable in all clients or servers. Interface ResponseMessage extends Message $ Notifications and Requests (Prior versions of the protocol used the string constant utf8 which is not a correct encoding constant according to specification.) For backwards compatibility it is highly recommended that a client and a server treats the string utf8 as utf-8. If a server or client receives a header with a different encoding than utf-8 it should respond with an error. It defaults to utf-8, which is the only encoding supported right now. The content part is encoded using the charset provided in the Content-Type field.

The content part of a message uses JSON-RPC to describe requests, responses and notifications. Content PartĬontains the actual content of the message.

This includes the ‘ ’ separating the header and content part. The header part is encoded using the ‘ascii’ encoding. Defaults to application/vscode-jsonrpc charset=utf-8 Considering the last header field and the overall header itself are each terminated with ‘ ’, and that at least one header is mandatory, this means that two ‘ ’ sequences always immediately precede the content part of a message.Ĭurrently the following header fields are supported: Header Field Name Each header field is terminated by ‘ ’. The structure of header fields conform to the HTTP semantic. Each header field is comprised of a name and a value, separated by ‘: ‘ (a colon and a space). The header part consists of header fields. The base protocol consists of a header and a content part (comparable to HTTP). Features in the spec are kept compatible using so called capability flags which are exchanged between the client and the server during initialization. The version of the specification is used to group features into a new specification release and to refer to their first appearance. Change annotation support for text edits and file operations (create, rename, delete)Ī detailed list of the changes can be found in the change log.Events for file operations (create, rename, delete).What’s new in 3.16Īll new 3.16 features are tagged with a corresponding since version 3.16 text or in JSDoc using 3.16.0 annotation.

Note: edits to this specification can be made via a pull request against this markdown document.

An implementation for node of the 3.16.x version of the protocol can be found here. This document describes the 3.16.x version of the language server protocol.

Transfer characters from microsoft private character editor