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
The LSP specification says that all code will be transported over UTF-8 in a JSON object. However it sends position as the UTF-16 representation. Yes this is dumb, but while it stays this way we must conform to it. So if anyone could do an internal text representation module that supports the TextEdit specification from the spec it would be really helpful for when we can start implementing the actual functionality.
The text was updated successfully, but these errors were encountered:
The LSP specification says that all code will be transported over UTF-8 in a JSON object. However it sends position as the UTF-16 representation. Yes this is dumb, but while it stays this way we must conform to it. So if anyone could do an internal text representation module that supports the TextEdit specification from the spec it would be really helpful for when we can start implementing the actual functionality.
The text was updated successfully, but these errors were encountered: