You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens because VSCode (or IDEs) expect positions to be calculated using the positionEncoding (see Client capability). pygls has convenient helpers for this, see PositionCodec.
Client and Server has to agree on which encoding they use for positions. Clients report the encodings they support via the positionEncoding field of Client Capability (missing this field means UTF-16 by default). Server has to pick one out of the offered encodings (again missing means UTF-16).
The text was updated successfully, but these errors were encountered:
Thanks for reporting. That's something my Rust LSP rewrite prototype handles already, but we should backport the functionality to our Python version if we can't find the time to finish the prototype soonish.
This happens because VSCode (or IDEs) expect positions to be calculated using the
positionEncoding
(see Client capability).pygls
has convenient helpers for this, seePositionCodec
.Client and Server has to agree on which encoding they use for positions. Clients report the encodings they support via the
positionEncoding
field of Client Capability (missing this field means UTF-16 by default). Server has to pick one out of the offered encodings (again missing means UTF-16).The text was updated successfully, but these errors were encountered: