protocol

type ClientCapabilities struct {
	protocol316.ClientCapabilities

	TextDocument *TextDocumentClientCapabilities `json:"textDocument,omitempty"`
}

type DiagnosticClientCapabilities struct {
	/**
	 * Whether implementation supports dynamic registration. If this is set to
	 * `true` the client supports the new
	 * `(TextDocumentRegistrationOptions & StaticRegistrationOptions)`
	 * return value for the corresponding server capability as well.
	 */
	DynamicRegistration bool `json:"dynamicRegistration"`

	/**
	 * Whether the clients supports related documents for document diagnostic
	 * pulls.
	 */
	RelatedDocumentSupport bool `json:"relatedDocumentSupport"`
}

type DiagnosticOptions struct {
	protocol316.WorkDoneProgressOptions
	/**
	 * An optional identifier under which the diagnostics are
	 * managed by the client.
	 */
	Identifier *string `json:"identifier"`

	/**
	 * Whether the language has inter file dependencies meaning that
	 * editing code in one file can result in a different diagnostic
	 * set in another file. Inter file dependencies are common for
	 * most programming languages and typically uncommon for linters.
	 */
	InterFileDependencies bool `json:"interFileDependencies"`

	/**
	 * The server provides support for workspace diagnostics as well.
	 */
	WorkspaceDiagnostics bool `json:"workspaceDiagnostics"`
}

type DiagnosticRegistrationOptions struct {
	protocol316.TextDocumentRegistrationOptions
	DiagnosticOptions
	protocol316.StaticRegistrationOptions
}

type DiagnosticServerCancellationData struct {
	RetriggerRequest bool `json:"retriggerRequest"`
}

type DocumentDiagnosticParams struct {
	protocol316.WorkDoneProgressParams
	protocol316.PartialResultParams

	/**
	 * The text document.
	 */
	TextDocument protocol316.TextDocumentIdentifier `json:"textDocument"`

	/**
	 * The additional identifier  provided during registration.
	 */
	Identifier *string `json:"identifier,omitempty"`

	/**
	 * The result id of a previous response if provided.
	 */
	PreviousResultId *string `json:"previousResultId,omitempty"`
}

type DocumentDiagnosticReport any // RelatedFullDocumentDiagnosticReport | RelatedUnchangedDocumentDiagnosticReport

type DocumentDiagnosticReportKind string

type DocumentDiagnosticReportPartialResult struct {
	RelatedDocuments map[protocol316.DocumentUri]interface{} `json:"relatedDocuments"`
}

type FullDocumentDiagnosticReport struct {
	/**
	 * A full document diagnostic report.
	 */
	Kind string `json:"kind"`

	/**
	 * An optional result id. If provided it will
	 * be sent on the next diagnostic request for the
	 * same document.
	 */
	ResultID *string `json:"resultId,omitempty"`

	/**
	 * The actual items.
	 */
	Items []protocol316.Diagnostic `json:"items"`
}

type Handler struct {
	protocol316.Handler

	Initialize             InitializeFunc
	TextDocumentDiagnostic TextDocumentDiagnosticFunc
	// contains filtered or unexported fields
}

type InitializeFunc func(context *glsp.Context, params *InitializeParams) (any, error)

type InitializeParams struct {
	protocol316.InitializeParams

	/**
	 * The capabilities provided by the client (editor or tool)
	 */
	Capabilities ClientCapabilities `json:"capabilities"`
}

type InitializeResult struct {
	/**
	 * The capabilities the language server provides.
	 */
	Capabilities ServerCapabilities `json:"capabilities"`

	/**
	 * Information about the server.
	 *
	 * @since 3.15.0
	 */
	ServerInfo *protocol316.InitializeResultServerInfo `json:"serverInfo,omitempty"`
}

type RelatedFullDocumentDiagnosticReport struct {
	FullDocumentDiagnosticReport
	/**
	 * Diagnostics of related documents. This information is useful
	 * in programming languages where code in a file A can generate
	 * diagnostics in a file B which A depends on. An example of
	 * such a language is C/C++ where marco definitions in a file
	 * a.cpp and result in errors in a header file b.hpp.
	 *
	 * @since 3.17.0
	 */
	RelatedDocuments map[protocol316.DocumentUri]interface{} `json:"relatedDocuments,omitempty"`
}

type RelatedUnchangedDocumentDiagnosticReport struct {
	UnchangedDocumentDiagnosticReport
	/**
	 * Diagnostics of related documents. This information is useful
	 * in programming languages where code in a file A can generate
	 * diagnostics in a file B which A depends on. An example of
	 * such a language is C/C++ where marco definitions in a file
	 * a.cpp and result in errors in a header file b.hpp.
	 *
	 * @since 3.17.0
	 */
	RelatedDocuments map[protocol316.DocumentUri]interface{} `json:"relatedDocuments,omitempty"`
}

type ServerCapabilities struct {
	protocol316.ServerCapabilities

	/**
	 * The server has support for pull model diagnostics.
	 *
	 * @since 3.17.0
	 */
	DiagnosticProvider any `json:"diagnosticProvider,omitempty"` // nil | DiagnosticOptions | DiagnosticRegistrationOptions
}

type TextDocumentClientCapabilities struct {
	protocol316.TextDocumentClientCapabilities

	/**
	 * Capabilities specific to the diagnostic pull model.
	 *
	 * @since 3.17.0
	 */
	Diagnostic *DiagnosticClientCapabilities `json:"diagnostic,omitempty"`
}

type TextDocumentDiagnosticFunc func(context *glsp.Context, params *DocumentDiagnosticParams) (any, error)

type UnchangedDocumentDiagnosticReport struct {
	/**
	 * A document diagnostic report indicating
	 * no changes to the last result. A server can
	 * only return `unchanged` if result ids are
	 * provided.
	 */
	Kind string `json:"kind"`

	/**
	 * A result id which will be sent on the next
	 * diagnostic request for the same document.
	 */
	ResultID string `json:"resultId"`
}