DOCUMENTATION: https://microsoft.github.io/language-server-protocol/

• LSP uses JSDoc for documentation
• Change Log:
  • https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#version_3_17_0
• `\r\n` is used as the main delimiter in the protocol
  • Used to terminate field entries in the header
  • Used again to separate the header from the content
• Header has only 2 supported fields:
  • Content-Length
  • Content-Type
    • See the following for valid content-types:
      • https://stackoverflow.com/a/23714451
      • https://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-26.html#rfc.section.3.1.1.5
• Content: goes over this in detail, but is pretty much just the JSON response/request
• After a quick review of JSON-RPC used in the spec, JSON-RPC isn't JSON, but JSON-based?? Great, now I gotta learn another language :(
  • JSON-RPC spec:
    • https://www.jsonrpc.org/specification
  • Nevermind, the API for it is just written in TypeScript for some ungodly reason (Do I really need type safety for an API description??)
• The spec enforces the use ECMAScript Regex in messages. (Will this be an issue in PowerShell or C#?)
• Holy moly this doc is humungous