Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/tools/gopls: textEdit calculation wrong. #57384

Closed
phakepraful opened this issue Dec 17, 2022 · 3 comments
Closed

x/tools/gopls: textEdit calculation wrong. #57384

phakepraful opened this issue Dec 17, 2022 · 3 comments
Labels
FrozenDueToAge gopls Issues related to the Go language server, gopls. Tools This label describes issues relating to any tools in the x/tools repository.

Comments

@phakepraful
Copy link

gopls version

0.11.0

gopls -v version Build info ---------- golang.org/x/tools/gopls v0.11.0 golang.org/x/tools/[email protected] h1:/nvKHdTtePQmrv9XN3gIUN9MOdUrKzO/dcqgbG6x8EY= github.com/BurntSushi/[email protected] h1:9F2/+DoOYIOksmaJFPw1tGFy1eDnIJXg+UHjuD8lTak= github.com/google/[email protected] h1:O2Tfq5qg4qc4AmwVlvv0oLiVAGB7enBSJ2x2DqQFi38= github.com/sergi/[email protected] h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0= golang.org/x/[email protected] h1:QfTh0HpN6hlw6D3vu8DAwC8pBIwikq0AI1evdm+FksE= golang.org/x/exp/[email protected] h1:fl8k2zg28yA23264d82M4dp+YlJ3ngDcpuB1bewkQi4= golang.org/x/[email protected] h1:LapD9S96VoQRhi/GrNTqeBJFrUjs5UHCAtTlgwA5oZA= golang.org/x/[email protected] h1:wsuoTGHzEhffawBOhz5CYhcrV4IdKZbEyZjBMuTp12o= golang.org/x/[email protected] h1:ljd4t30dBnAvMZaQCevtY0xLLD0A+bRZXbgLMLU1F/A= golang.org/x/[email protected] h1:BrVqGRd7+k1DiOgtnFvAkoQEWQvBc25ouMJM6429SFg= golang.org/x/[email protected] h1:7/HkGkN/2ktghBCSRRgp31wAww4syfsW52tj7yirjWk= golang.org/x/[email protected] h1:qptQiQwEpETwDiz85LKtChqif9xhVkAm8Nhxs0xnTww= honnef.co/go/[email protected] h1:oDx7VAwstgpYpb3wv0oxiZlxY+foCpRAwY7Vk6XpAgA= mvdan.cc/[email protected] h1:JVf4NN1mIpHogBj7ABpgOyZc65/UUOkKQFkoURsz4MM= mvdan.cc/xurls/[email protected] h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc= go: go1.19.2

go env

go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\x\AppData\Local\go-build
set GOENV=C:\Users\x\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\x\Go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\x\Go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=H:\Software\Scoop\apps\go\current
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=H:\Software\Scoop\apps\go\current\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.19.2
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=C:\Users\x\AppData\Local\Temp\go-build3329400193=/tmp/go-build -gno-record-gcc-switches

What did you do?

  1. Create test file.
  2. Declare package, import testing.
  3. Type "func Te"
package something

import "testing"

func Te

206698487-0f6887d2-174a-4d6c-a704-2430d676a565

What did you expect to see?

package something

import "testing"

func TestXxx|(t *testing.T){

}

What did you see instead?

package something

import "testing"

func TeTestXxx|(t *testing.T){

}

Editor and settings

Neovim with nvim-lspconfig. Default settings.

Logs

[Trace - 14:50:54.916 PM] Received response 'textDocument/completion - (117)' in 0ms.
"Result":{
   "isIncomplete":true,
   "items":[
      {
         "label":"TestXxx(t *testing.T)",
         "kind":3,
         "detail":"tab, type the rest of the name, then tab",
         "documentation":"Test test function",
         "preselect":true,
         "sortText":"00000",
         "insertTextFormat":2,
         "textEdit":{
            "range":{
               "start":{
                  "line":4,
                  "character":5
               },
               "end":{
                  "line":4,
                  "character":5
               }
            },
            "newText":"Test${1:Xxx}(t *testing.T) {\n$0\n\\}"
         }
      },
      {
         "label":"TestMain(m *testing.M)",
         "kind":3,
         "documentation":"complete the parameter",
         "sortText":"00001",
         "filterText":"TestMain(m *testing.M)",
         "insertTextFormat":2,
         "textEdit":{
            "range":{
               "start":{
                  "line":4,
                  "character":5
               },
               "end":{
                  "line":4,
                  "character":5
               }
            },
            "newText":"TestMain(m *testing.M)"
         }
      }
   ]
}

gopls.log relevant textEdit at 14:50:54.916 PM

@gopherbot gopherbot added Tools This label describes issues relating to any tools in the x/tools repository. gopls Issues related to the Go language server, gopls. labels Dec 17, 2022
@gopherbot gopherbot added this to the Unreleased milestone Dec 17, 2022
@findleyr
Copy link
Contributor

CC @pjweinb

We'll investigate and try to fix this for the next release. I suspect this may have to do with configured completion options / capabilities, as it doesn't seem to affect all clients.

@findleyr findleyr modified the milestones: Unreleased, gopls/v0.12.0 Dec 20, 2022
@findleyr
Copy link
Contributor

@pjweinb and I looked into this. These edits may be technically correct, based on the LSP spec:
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion

There is discussion there of filtering based on word boundaries. In particular, there is the following statement: "If you create a completion item with a text edit at the current cursor position no word guessing takes place and no filtering should happen." But that is not what gopls does: it provides a completion positioned at the start of the Te identifier, and so clients such as VS Code filter these results based on the existing text, and this completion works as expected.

With that said the spec seems a bit vague, and I don't know why we couldn't provide a text edit at the current cursor position, which would be unambigious. We're investigating what this would entail.

@findleyr
Copy link
Contributor

Aha, this is a dupe of #56852. Moving discussion over there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge gopls Issues related to the Go language server, gopls. Tools This label describes issues relating to any tools in the x/tools repository.
Projects
None yet
Development

No branches or pull requests

3 participants