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
Some LSP clients (ahem, Gnome Builder) don't respect our choice for full text synchronization, and it wouldn't hurt to reduce the amount of text transferred.
The text change notification comes in here. params.content_changes contains all changes, but right now we only process one of them. Before passing the changes to the VFS layer, we need to convert from a line/column to byte offset representation. The latter is implemented as the TextRange type, and a conversion method is available here.
The text was updated successfully, but these errors were encountered:
Another potential complication is that we store files with normalized line endings (\n), so we need to account for that. I think just normalizing the text from TextDocumentContentChangeEvent would do the trick, as ranges are ending-agnosic.
Spawned off #3758.
Some LSP clients (ahem, Gnome Builder) don't respect our choice for full text synchronization, and it wouldn't hurt to reduce the amount of text transferred.
The text change notification comes in here.
params.content_changes
contains all changes, but right now we only process one of them. Before passing the changes to the VFS layer, we need to convert from a line/column to byte offset representation. The latter is implemented as theTextRange
type, and a conversion method is available here.The text was updated successfully, but these errors were encountered: