1
0
mirror of https://github.com/golang/go synced 2024-11-18 08:44:43 -07:00
go/gopls
Iskander Sharipov b1451cf344 gopls/integration: remove commented-out debug code
Change-Id: I824a36f893970588534ec85ade93dfa100d14fe6
Reviewed-on: https://go-review.googlesource.com/c/tools/+/209697
Run-TryBot: Iskander Sharipov <quasilyte@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Peter Weinberger <pjw@google.com>
2019-12-03 23:32:40 +00:00
..
doc internal/lsp: link to the new pkg.go.dev instead of godoc.org 2019-11-30 07:06:09 +00:00
integration gopls/integration: remove commented-out debug code 2019-12-03 23:32:40 +00:00
internal/hooks internal/lsp: set version correctly after textDocument/didOpen 2019-11-25 19:35:51 +00:00
test gopls: control features for command line tests 2019-11-07 01:09:34 +00:00
go.mod gopls: update go.mod file 2019-10-21 18:45:54 +00:00
go.sum gopls: use go-diff for edit generation 2019-10-10 20:18:25 +00:00
main.go internal/lsp: use options hooks to install diff driver 2019-10-11 16:38:31 +00:00
README.md cmd/gopls: add documentation 2019-08-27 15:23:08 +00:00

gopls documentation

gopls (pronounced: "go please") is the official language server for the Go language.

It is currently in alpha, so it is not stable. You can see more information about the status of gopls and its supported features here.

In general you should not need to know anything about gopls, it should be integrated into your editor for you.

See the installing section of the user guide if you need to install or update gopls by hand.

Issues

If you are having issues with gopls, please first check the known issues before following the troubleshooting guide. If that does not give you the information you need, reach out to us.

You can chat with us on:

If you think you have an issue that needs fixing, or a feature suggestion, then please make sure you follow the steps to file an issue with the right information to allow us to address it.

If you need to talk to us directly (for instance to file an issue with confidential information in it) you can reach out directly to @stamblerre or @ianthehat.

More information

If you want to know more about it, have an unusual use case, or want to contribute, please read the following documents