class

LSProtocol::CodeActionClientCapabilities

Inherits JSON::Serializable / Reference / Object

The Client Capabilities of a CodeActionRequest.

Constructors

new(pull : JSON::PullParser)
Source
new(code_action_literal_support : ClientCodeActionLiteralOptions | Nil = nil, data_support : Bool | Nil = nil, disabled_support : Bool | Nil = nil, documentation_support : Bool | Nil = nil, dynamic_registration : Bool | Nil = nil, honors_change_annotations : Bool | Nil = nil, is_preferred_support : Bool | Nil = nil, resolve_support : ClientCodeActionResolveOptions | Nil = nil, tag_support : CodeActionTagOptions | Nil = nil)
Source
new(*, __pull_for_json_serializable pull : JSON::PullParser)
Source

Instance methods

code_action_literal_support

The client support code action literals of type CodeAction as a valid response of the textDocument/codeAction request. If the property is not set the request can only return Command literals.

@since 3.8.0

Source
data_support

Whether code action supports the data property which is preserved between a textDocument/codeAction and a codeAction/resolve request.

@since 3.16.0

Source
disabled_support

Whether code action supports the disabled property.

@since 3.16.0

Source
documentation_support

Whether the client supports documentation for a class of code actions.

@since 3.18.0 @proposed

Source
dynamic_registration

Whether code action supports dynamic registration.

Source
honors_change_annotations

Whether the client honors the change annotations in text edits and resource operations returned via the CodeAction#edit property by for example presenting the workspace edit in the user interface and asking for confirmation.

@since 3.16.0

Source
is_preferred_support

Whether code action supports the isPreferred property.

@since 3.15.0

Source
resolve_support

Whether the client supports resolving additional code action properties via a separate codeAction/resolve request.

@since 3.16.0

Source
tag_support

Client supports the tag property on a code action. Clients supporting tags have to handle unknown tags gracefully.

@since 3.18.0 - proposed

Source