Structs§
- Client
- A handle for sending server-to-client messages, such as
textDocument/publishDiagnostics. - Notification
- A notification message. A processed notification message must not send a response back. They work like events.
- Request
- A request message to describe a request between the client and the server. Every processed request must send a response back to the sender of the request.
- Response
Error - The error a
Handleranswers a request with: what went wrong, and the message the client shows. - Server
- A set of Sender/Receiver objects for passing
Messages around. - Thread
Connection - Tracing
Layer
Enums§
- Error
Code - An ErrorCode representing either a JSON-RPC Error Code or LSP defined error code.
- Id
- A identifier for tracking
Requests andResponses. An identifier can be a String or Number if included. - Message
- JSON RPC Message
This represents a single message coming in or going out, that is
compliant with the JSON-RPC 2.0 spec.
It wraps the
Request,ResponseandNotificationstructs. - Message
Error - Parse
Error - Position
Encoding - The unit that LSP [
Position::character] offsets count, agreed with the client duringinitialize. - Response
- A Response Message sent as a result of a request