3f4d10fc73
Use ast.IsExported instead of explicit code. Change-Id: I1bfabb3c575debb699a51e38f502fcb99a081203 Reviewed-on: https://go-review.googlesource.com/c/tools/+/216297 Run-TryBot: Peter Weinberger <pjw@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org> |
||
|---|---|---|
| .. | ||
| 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 directore (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.