b15dac2b88
This CL was created using the following commands:
./gopls/internal/migrate.sh
git add .
git codereview gofmt
For golang/go#54509
Change-Id: Iceeec602748a5e6f609c3ceda8d19157e5c94009
Reviewed-on: https://go-review.googlesource.com/c/tools/+/426796
gopls-CI: kokoro <noreply+kokoro@google.com>
Run-TryBot: Robert Findley <rfindley@google.com>
Reviewed-by: Peter Weinberger <pjw@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
|
||
|---|---|---|
| .. | ||
| README.md | ||
| helper.go | ||
README.md
Generate server_gen.go
helper generates boilerplate code for server.go by processing the
generated code in protocol/tsserver.go.
First, build helper in this directory (go build .).
In directory lsp, executing go generate server.go generates the stylized file
server_gen.go that contains stubs for type Server.
It decides what stubs are needed and their signatures
by looking at the Server interface (-t flag). These all look somewhat like
Resolve(context.Context, *CompletionItem) (*CompletionItem, error).
It then parses the lsp directory (-u flag) to see if there is a corresponding
implementation function (which in this case would be named resolve). If so
it discovers the parameter names needed, and generates (in server_gen.go) code
like
func (s *Server) resolve(ctx context.Context, params *protocol.CompletionItem) (*protocol.CompletionItem, error) {
return s.resolve(ctx, params)
}
If resolve is not defined (and it is not), then the body of the generated function is
return nil, notImplemented("resolve")
So to add a capability currently not implemented, just define it somewhere in lsp.
In this case, just define func (s *Server) resolve(...) and re-generate server_gen.go.