1
0
mirror of https://github.com/golang/go synced 2024-09-30 14:28:33 -06:00
go/gopls
Ian Cottrell f79515f338 gopls: control features for command line tests
A general mechanism for modifying the features in command line tests
Use it to turn of go-diff for now

Fixes golang/go#35392

Change-Id: Ie79723e94fb14fcde1e98709a63f44046e101bc4
Reviewed-on: https://go-review.googlesource.com/c/tools/+/205739
Run-TryBot: Ian Cottrell <iancottrell@google.com>
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-11-07 01:09:34 +00:00
..
doc Fix header level in settings.md 2019-10-28 21:55:54 +00:00
internal/hooks internal/lsp: use options hooks to install diff driver 2019-10-11 16:38:31 +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