Version 3.17 of the spec added a position_encoding field in the ServerCapabilities, so use that.
Note that the spec says that UTF-16 is mendatory, and vscode only support utf-16, meaning we currently have a bug when having non-ascii in the source (#5669)
Version 3.17 of the spec added a
position_encoding
field in the ServerCapabilities, so use that.Note that the spec says that UTF-16 is mendatory, and vscode only support utf-16, meaning we currently have a bug when having non-ascii in the source (#5669)