diff options
| author | Florian Fischer <florian.fl.fischer@fau.de> | 2021-02-15 11:46:34 +0100 |
|---|---|---|
| committer | Florian Fischer <florian.fl.fischer@fau.de> | 2021-02-15 11:46:34 +0100 |
| commit | 188b64a4676e476321f115673f0d2bb77c1cd7e1 (patch) | |
| tree | 98c9df78ed6c28b1a7df5f6897f7c316e70b3cf7 | |
| parent | f4c2ba186a01a036360eae27db7616cbcf92ebda (diff) | |
| download | vis-lspc-188b64a4676e476321f115673f0d2bb77c1cd7e1.tar.gz vis-lspc-188b64a4676e476321f115673f0d2bb77c1cd7e1.zip | |
[README] reflect didChange implementation
| -rw-r--r-- | README.md | 5 |
1 files changed, 2 insertions, 3 deletions
@@ -15,12 +15,11 @@ vis-lspc currently supports: Everything else. -Especially `textDocument/didChange` must be implemented before vis-lspc is somewhat usable. -To my knowledge the is currently no good way to detect file changes vis the Lua API. +To my knowledge there is currently no good way to detect file changes via the Lua API. But this is essential to support [Text Synchronization](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#textSynchronization) which is required by the LSP protocol. -A dirty workaround could be to send the whole file content in a `textDocument/didChange` +A dirty workaround we currently use is to send the whole file content in a `textDocument/didChange` method call before calling any other method. If someone can come up with an idea how to solve this I would appreciate contributions. |