@ardan-bkennedy suggested that we should try to use the progress reporting functionality of LSP to indicate when a module is being downloaded by go/packages. Otherwise, we just have a slow save that don't give the user any indication that gopls is communicating with the network.
This will be tricky because only go/packages knows that it's downloading a module. My current best guess at how to do this is to put something in the config's Logf function...or maybe use a trick like packagesinternal?
The text was updated successfully, but these errors were encountered:
If the internal/telemetry experiment is a success we could instrument the go/packages library using it and then gopls could register an exporter that tracks progress and reports it easily (the same way it already intercepts log messages and sends them as "window/logMessage")
It would also replace the existing Logf hooks in a much cleaner way.