Registration options for a CompletionRequest.

Fields

@:optionaloptionalworkDoneProgress:Null<Bool>

@:optionaloptionaltriggerCharacters:Null<Array<String>>

Most tools trigger completion request automatically without explicitly requesting it using a keyboard shortcut (e.g. Ctrl+Space). Typically they do so when the user starts to type an identifier. For example if the user types c in a JavaScript file code complete will automatically pop up present console besides others as a completion item. Characters that make up identifiers don't need to be listed here.

If code complete should automatically be trigger on characters not being valid inside an identifier (for example . in JavaScript) list them in triggerCharacters.

@:optionaloptionalresolveProvider:Null<Bool>

The server provides support to resolve additional information for a completion item.

documentSelector:Null<DocumentSelector>

A document selector to identify the scope of the registration. If set to null the document selector provided on the client side will be used.

@:optionaloptionalcompletionItem:Null<{labelDetailsSupport:Null<Bool>}>

The server supports the following CompletionItem specific capabilities.

Available since

3.17.0

.

@:optionaloptionalallCommitCharacters:Null<Array<String>>

The list of all possible characters that commit a completion. This field can be used if clients don't support individual commmit characters per completion item. See ClientCapabilities.textDocument.completion.completionItem.commitCharactersSupport

If a server provides both allCommitCharacters and commit characters on an individual completion item the ones on the completion item win.

Available since

3.2.0

.