The edge cases in different editors with regards to word boundaries has been too high (even for syntaxes in the same editor).
Since perhaps not all clients support it, adopting this without checking for clientCapabilities would be a breaking change. We keep the existing behavior for backwards compatibility. Nevermind, I'm looking at it wrong. From 3.16 is the new InsertReplaceEdit. textEdit is as old as the spec.
TODO:
[x] Add textEdit variant of all completion items.
[x] Use clientCapabilities to decide whether or not snippets should be used (while we're at it)
[x] Manual testing in VS Code
[x] Manual testing in Sublime Text
[x] Manual testing Helix
[x] Update the automated tests with new assertions
The edge cases in different editors with regards to word boundaries has been too high (even for syntaxes in the same editor).
Since perhaps not all clients support it, adopting this without checking for clientCapabilities would be a breaking change. We keep the existing behavior for backwards compatibility.Nevermind, I'm looking at it wrong. From 3.16 is the new InsertReplaceEdit.textEditis as old as the spec.TODO:
Replaces #231
For #230