Theia no longer comes with basic go support, si this extension should register the language and add the grammar and configuration.

see

• https://github.com/Microsoft/monaco-languages/tree/master/src/go (language config)
• https://github.com/Microsoft/vscode/tree/master/extensions/go/syntaxes (textmate grammar)
• https://github.com/theia-ide/theia/pull/2253/commits/1b81563144d802580ade4863b8130119aac77d29 (example)

When Network is not very fast Theia becomes unusable and keyboard is no accepting input or the input is showing after delay.

Maybe related: at times, it seems like the editor rolls-back some typed characters. We do not know for sure, but one hypothesis is that adverse network conditions causes some editor updates to be lost, after being echo'ed in the editor. e.g. you type "example" and see it in the editor, then the last few characters disappear and we are left with "examp".

I think the latest published version of this extension might be is wrong. I would expect it to map to version 0.3.x, but it seems it instead points to "0.4.0-next.eaea5735".

$ npm view @theia/go | grep latest
  'dist-tags': { next: '0.4.0-next.5b821fb9', latest: '0.4.0-next.eaea5735' },

This might be an issue if we have "latest" version of @theia/go, as a dependency of a theia application, as then it seems to transitively pulls the next version of @theia/core, which results in:

Example package.json:

{
    "private": true,
    "dependencies": {
        "@theia/core": "latest",
        "@theia/cpp": "latest",
        "@theia/editor": "latest",
        "@theia/extension-manager": "latest",
        "@theia/file-search": "latest",
        "@theia/filesystem": "latest",
        "@theia/git": "latest",
        "@theia/java":"latest",
        "@theia/languages": "latest",
        "@theia/markers": "latest",
        "@theia/messages": "latest",
        "@theia/metrics": "latest",
        "@theia/monaco": "latest",
        "@theia/navigator": "latest",
        "@theia/outline-view": "latest",
        "@theia/preferences": "latest",
        "@theia/process": "latest",
        "@theia/python": "latest",
        "@theia/terminal": "latest",
        "@theia/typescript": "latest",
        "@theia/userstorage": "latest",
        "@theia/go": "latest"
    },
    "devDependencies": {
        "@theia/cli": "latest"
    }
}

'Show all commands' yields a list of all commands which are rendered as buttons. As they are too many, you can only see the some of them, the rest is outside the viewport.

It looks like the last build didn't pass: https://travis-ci.org/theia-ide/theia-php-extension/builds/499128046 would you please re-run the build so it will publish an updated package to npm?

Currently, the commands go into the context menu and are not bound to any keys. We should decide which commands should be in the menu, which should have keybindings

Theia/Monaco LC now uses a singleton command registry. As a consequence, our hooks to set labels and isVisible() on the server side commands are no longer called.

As a result, Go editor context menu entries are visible on all editors, not just go, and the other commands don't appear in the quick command list, as they have no label.

Hello,

I'm giving the extension a go (heh), but I haven't been able to format the code, automatically nor manually. Choosing Format document/selection doesn't seem to do anything - no errors either - although code intellisense seems to be working correctly. My gopath is set, and it includes the dependencies listed in the prerequisites for Go LSP. I'm running the latest versions ("next" tag), with Go 1.11.4. Am I doing something wrong or is there no formatting?

The command line tools the go LS delegates to needs GOPATH to be defined correctly to find references across files. By default, it assumes GOPATH=<home>/go. If you have your workspace located elsewhere, find references and other services relying on it (code lens, call hierarchy...) will not work across file borders.

On the Go homepage they state "Go programmers typically keep all their Go code in a single workspace.". If that was true, a globally set GOPATH would suffice.

Nevertheless, in the IDE scenario it appears that you are more likely to work with a local GOPATH pointing to your workspace root. That is why vscode/go allows to set it in the config in various ways. Our Go LS supports exactly that, so you can override it in

• <home>/.go/go.json
• <wsroot>/go.json
• <wsfolder-root>/go.json (AFAIK, Theia does not support workspace folders yet,so this is 'for future use')

e.g.

{
    "inferGopath": true
}

Should we make that setting the default? I can imagine that it can also cause a lot of confusion for those users who stick to the Go recommendation. Go experts, what is your opinion?