|
/** |
|
* Workspace specific client capabilities. |
|
*/ |
|
workspace?: { |
|
/** |
|
* The client supports applying batch edits |
|
* to the workspace by supporting the request |
|
* 'workspace/applyEdit' |
|
*/ |
|
applyEdit?: boolean; |
|
|
|
/** |
|
* Capabilities specific to `WorkspaceEdit`s |
|
*/ |
|
workspaceEdit?: WorkspaceEditClientCapabilities; |
|
|
|
/** |
|
* Capabilities specific to the `workspace/didChangeConfiguration` |
|
* notification. |
|
*/ |
|
didChangeConfiguration?: DidChangeConfigurationClientCapabilities; |
|
|
|
/** |
|
* Capabilities specific to the `workspace/didChangeWatchedFiles` |
|
* notification. |
|
*/ |
|
didChangeWatchedFiles?: DidChangeWatchedFilesClientCapabilities; |
|
|
|
/** |
|
* Capabilities specific to the `workspace/symbol` request. |
|
*/ |
|
symbol?: WorkspaceSymbolClientCapabilities; |
|
|
|
/** |
|
* Capabilities specific to the `workspace/executeCommand` request. |
|
*/ |
|
executeCommand?: ExecuteCommandClientCapabilities; |
|
|
|
/** |
|
* The client has support for workspace folders. |
|
* |
|
* @since 3.6.0 |
|
*/ |
|
workspaceFolders?: boolean; |
|
|
|
/** |
|
* The client supports `workspace/configuration` requests. |
|
* |
|
* @since 3.6.0 |
|
*/ |
|
configuration?: boolean; |
|
|
|
/** |
|
* Capabilities specific to the semantic token requests scoped to the |
|
* workspace. |
|
* |
|
* @since 3.16.0 |
|
*/ |
|
semanticTokens?: SemanticTokensWorkspaceClientCapabilities; |
|
|
|
/** |
|
* Capabilities specific to the code lens requests scoped to the |
|
* workspace. |
|
* |
|
* @since 3.16.0 |
|
*/ |
|
codeLens?: CodeLensWorkspaceClientCapabilities; |
|
|
|
/** |
|
* The client has support for file requests/notifications. |
|
* |
|
* @since 3.16.0 |
|
*/ |
|
fileOperations?: { |
|
/** |
|
* Whether the client supports dynamic registration for file |
|
* requests/notifications. |
|
*/ |
|
dynamicRegistration?: boolean; |
|
|
|
/** |
|
* The client has support for sending didCreateFiles notifications. |
|
*/ |
|
didCreate?: boolean; |
|
|
|
/** |
|
* The client has support for sending willCreateFiles requests. |
|
*/ |
|
willCreate?: boolean; |
|
|
|
/** |
|
* The client has support for sending didRenameFiles notifications. |
|
*/ |
|
didRename?: boolean; |
|
|
|
/** |
|
* The client has support for sending willRenameFiles requests. |
|
*/ |
|
willRename?: boolean; |
|
|
|
/** |
|
* The client has support for sending didDeleteFiles notifications. |
|
*/ |
|
didDelete?: boolean; |
|
|
|
/** |
|
* The client has support for sending willDeleteFiles requests. |
|
*/ |
|
willDelete?: boolean; |
|
}; |
|
|
|
/** |
|
* Client workspace capabilities specific to inline values. |
|
* |
|
* @since 3.17.0 |
|
*/ |
|
inlineValue?: InlineValueWorkspaceClientCapabilities; |
|
|
|
/** |
|
* Client workspace capabilities specific to inlay hints. |
|
* |
|
* @since 3.17.0 |
|
*/ |
|
inlayHint?: InlayHintWorkspaceClientCapabilities; |
|
|
|
/** |
|
* Client workspace capabilities specific to diagnostics. |
|
* |
|
* @since 3.17.0. |
|
*/ |
|
diagnostics?: DiagnosticWorkspaceClientCapabilities; |
|
}; |
In the 3.18 version of the specs, the description for the Text Document Content Request mentions a
workspace.textDocumentContentpath in the client capabilitieslanguage-server-protocol/_specifications/lsp/3.18/workspace/textDocumentContent.md
Line 6 in d675b26
and this exists in the meta model at
language-server-protocol/_specifications/lsp/3.18/metaModel/metaModel.json
Lines 11310 to 11320 in d675b26
but it is not part of the ClientCapabilities in the specs:
language-server-protocol/_specifications/lsp/3.18/general/initialize.md
Lines 353 to 484 in d675b26