-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accept GOROOT configuration #42
Comments
The goroot is not provided in the Unfortunately 3.6 isn't implemented in the vscode-languageserver project yet, which we depend on. |
The NPM packages with new versions have been released. |
Paused again. We are running into a problem where we can't get the GOROOT information fast enough. After the Handler is created, we start processing the request queue. This is first routed through the Instead, we are going to try to manage this by first preloading the default GOROOT when the server starts. All workspaces, when they are first opened, will be evaluated against that environment. If later a configuration changed notification comes in which points to a different GOROOT, we will need to make sure that it's loaded, and then reload the workspace. In this way, we should also be able to change GOROOTs (and other configuration) on the fly without stopping the app or closing the workspace. |
Dependent on work started in #54 . |
The
InitializationParams
provided to theinitialize
JSONRPC2 method may include a custom GOROOT location, as specified by an editor. If so, override the runtime specified location in the loader.The text was updated successfully, but these errors were encountered: