oauth2 VS goimports

The guide covers setting up GitHub, using the golang.org/x/oauth2 package, and handling OAuth authentication. The code snippets are easy to follow and can be modified to fit your project's needs.

I personally use golang.org/x/oauth2 to handle OAuth in my app, so I'll use that for this example.

I mean using the OAuth2 client library that's maintained as part of the Go project.

My wife sent MR into golang oauth2 library https://github.com/golang/oauth2/pull/450

Hmm, this might be a relevant issue: https://github.com/golang/oauth2/issues/128 . On the face of it, it looks like https://github.com/coreos/go-oidc is a more thorough implementation...(?)

Handling auth in a Transport is a common pattern, that's what x/oauth2 does for example: https://github.com/golang/oauth2/blob/master/transport.go#L20

golang/oauth2 (Go): Go OAuth2

Just a guess, but it might be somewhere in gopls https://github.com/golang/tools/tree/master/gopls/doc On this page https://langserver.org/ it says it should support "finding references"

Language server protocol. Here’s a good one: https://github.com/golang/tools/blob/master/gopls/README.md

gopls was not able to find modules in your workspace.When outside of GOPATH, gopls needs to know which modules you are working on.You can fix this by opening your workspace to a folder inside a Go module, orby using a go.work file to specify multiple modules.See the documentation for more information on setting up your workspace:https://github.com/golang/tools/blob/master/gopls/doc/workspace.md.

For more gopls settings, you can see files in this folder: https://github.com/golang/tools/tree/master/gopls/doc

But finding which interface is satisfied by a type is trivial anyways through gopls which integrates conveniently into any LSP supporting IDE (such as VSCode and Goland).

You need to make sure you have Google's lsp server for golang installed.