First build with JSON RPC parsing
No responses or real functionality implemented
This commit is contained in:
commit
fcc15f5b68
9 changed files with 3910 additions and 0 deletions
90
src/lsp.h
Normal file
90
src/lsp.h
Normal file
|
|
@ -0,0 +1,90 @@
|
|||
#ifndef _LSP_H_
|
||||
#define _LSP_H_
|
||||
|
||||
#include <stdbool.h>
|
||||
#include <stdint.h>
|
||||
#include <string.h>
|
||||
|
||||
/* Ref: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/ */
|
||||
|
||||
typedef enum lsp_error_enum {
|
||||
// Defined by JSON-RPC
|
||||
LSP_ERR_ParseError = -32700,
|
||||
LSP_ERR_InvalidRequest = -32600,
|
||||
LSP_ERR_MethodNotFound = -32601,
|
||||
LSP_ERR_InvalidParams = -32602,
|
||||
LSP_ERR_InternalError = -32603,
|
||||
|
||||
/**
|
||||
* This is the start range of JSON-RPC reserved error codes.
|
||||
* It doesn't denote a real error code. No LSP error codes should
|
||||
* be defined between the start and end range. For backwards
|
||||
* compatibility the `ServerNotInitialized` and the `UnknownErrorCode`
|
||||
* are left in the range.
|
||||
*
|
||||
* @since 3.16.0
|
||||
*/
|
||||
LSP_ERR_jsonrpcReservedErrorRangeStart = -32099,
|
||||
/**
|
||||
* Error code indicating that a server received a notification or
|
||||
* request before the server received the `initialize` request.
|
||||
*/
|
||||
LSP_ERR_ServerNotInitialized = -32002,
|
||||
LSP_ERR_UnknownErrorCode = -32001,
|
||||
|
||||
/**
|
||||
* This is the end range of JSON-RPC reserved error codes.
|
||||
* It doesn't denote a real error code.
|
||||
*
|
||||
* @since 3.16.0
|
||||
*/
|
||||
LSP_ERR_jsonrpcReservedErrorRangeEnd = -32000,
|
||||
|
||||
/**
|
||||
* This is the start range of LSP reserved error codes.
|
||||
* It doesn't denote a real error code.
|
||||
*
|
||||
* @since 3.16.0
|
||||
*/
|
||||
LSP_ERR_lspReservedErrorRangeStart = -32899,
|
||||
|
||||
/**
|
||||
* A request failed but it was syntactically correct, e.g the
|
||||
* method name was known and the parameters were valid. The error
|
||||
* message should contain human readable information about why
|
||||
* the request failed.
|
||||
*
|
||||
* @since 3.17.0
|
||||
*/
|
||||
LSP_ERR_RequestFailed = -32803,
|
||||
|
||||
/**
|
||||
* The server cancelled the request. This error code should
|
||||
* only be used for requests that explicitly support being
|
||||
* server cancellable.
|
||||
*
|
||||
* @since 3.17.0
|
||||
*/
|
||||
LSP_ERR_ServerCancelled = -32802,
|
||||
|
||||
/**
|
||||
* The server detected that the content of a document got
|
||||
* modified outside normal conditions. A server should
|
||||
* NOT send this error code if it detects a content change
|
||||
* in its unprocessed messages. The result even computed
|
||||
* on an older state might still be useful for the client.
|
||||
*
|
||||
* If a client decides that a result is not of any use anymore
|
||||
* the client should cancel the request.
|
||||
*/
|
||||
LSP_ERR_ContentModified = -32801,
|
||||
|
||||
/**
|
||||
* The client has canceled a request and a server has detected
|
||||
* the cancel.
|
||||
*/
|
||||
LSP_ERR_RequestCancelled = -32800,
|
||||
} lsp_error_e;
|
||||
|
||||
#endif /* _LSP_H_ */
|
||||
|
||||
Loading…
Reference in a new issue