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. Major new feature are: type hierarchy, inline values, inlay hints, notebook document support and a meta model that describes the 3.17 LSP version.Ī detailed list of the changes can be found in the change log What’s new in 3.17Īll new 3.17 features are tagged with a corresponding since version 3.17 text or in JSDoc using 3.17.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.17.x version of the protocol can be found here. This document describes the 3.17.x version of the language server protocol.

Github workspaces