class LSProtocol::GeneralClientCapabilities
- LSProtocol::GeneralClientCapabilities
- Reference
- Object
Overview
General client capabilities.
@since 3.16.0
Included Modules
- JSON::Serializable
Defined in:
lsprotocol/types.crConstructors
- .new(pull : JSON::PullParser)
- .new(markdown : MarkdownClientCapabilities | Nil = nil, position_encodings : Array(PositionEncodingKind | String) | Nil = nil, regular_expressions : RegularExpressionsClientCapabilities | Nil = nil, stale_request_support : StaleRequestSupportOptions | Nil = nil)
Instance Method Summary
-
#markdown : MarkdownClientCapabilities | Nil
Client capabilities specific to the client's markdown parser.
-
#position_encodings : Array(PositionEncodingKind | String) | Nil
The position encodings supported by the client.
-
#regular_expressions : RegularExpressionsClientCapabilities | Nil
Client capabilities specific to regular expressions.
-
#stale_request_support : StaleRequestSupportOptions | Nil
Client capability that signals how the client handles stale requests (e.g.
Constructor Detail
Instance Method Detail
Client capabilities specific to the client's markdown parser.
@since 3.16.0
The position encodings supported by the client. Client and server have to agree on the same position encoding to ensure that offsets (e.g. character position in a line) are interpreted the same on both sides.
To keep the protocol backwards compatible the following applies: if the value 'utf-16' is missing from the array of position encodings servers can assume that the client supports UTF-16. UTF-16 is therefore a mandatory encoding.
If omitted it defaults to ['utf-16'].
Implementation considerations: since the conversion from one encoding into another requires the content of the file / line the conversion is best done where the file is read which is usually on the server side.
@since 3.17.0
Client capabilities specific to regular expressions.
@since 3.16.0
Client capability that signals how the client handles stale requests (e.g. a request for which the client will not process the response anymore since the information is outdated).
@since 3.17.0