internal/lsp: remove VS Code-specific completion hack
This hack was previously being used to correct the rankings for VS Code
Go users. This logic has since been moved into the VS Code Go plugin.
Change-Id: Ia6bff53eb2c6dbe479faa1fd0667d763837eea78
GitHub-Last-Rev: e7fed76b3f85b0db3b705cbb6945cecd855d2c7b
GitHub-Pull-Request: golang/tools#225
Reviewed-on: https://go-review.googlesource.com/c/tools/+/231098
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
diff --git a/internal/lsp/completion.go b/internal/lsp/completion.go
index bca9a83..e87876d 100644
--- a/internal/lsp/completion.go
+++ b/internal/lsp/completion.go
@@ -49,19 +49,6 @@
items := toProtocolCompletionItems(candidates, rng, options)
- if incompleteResults {
- for i := 1; i < len(items); i++ {
- // Give all the candidates the same filterText to trick VSCode
- // into not reordering our candidates. All the candidates will
- // appear to be equally good matches, so VSCode's fuzzy
- // matching/ranking just maintains the natural "sortText"
- // ordering. We can only do this in tandem with
- // "incompleteResults" since otherwise client side filtering is
- // important.
- items[i].FilterText = items[0].FilterText
- }
- }
-
return &protocol.CompletionList{
IsIncomplete: incompleteResults,
Items: items,
