Goland bazel plugin how to#
Goland bazel plugin install#
Goland bazel plugin update#
Goland bazel plugin code#

Goland bazel plugin update#

I usually update to the latest Goland version rather quickly, and I get annoyed when I get those 'the plugin is not compatible with your version of Goland' every day for a month or longer. I know that you are not the developer of the Bazel plugin, but you asked about the most annoying pain points, so it's part of the list. Thanks for collecting my feedback on the appropriate places :)

Goland bazel plugin how to#

You can make it visible to jetbrains-team only, and you can add the IDE logs, from Help | Collect Logs and Diagnostics Data, and a snapshot of the IDE while it's doing what causes it to 'nearly crash', see this document on how to get those snapshots. Opening a project with those folders nearly crashes Goland.ДЇor us to address it, it would be useful if you can please open an issue on our tracker at. by default bazel creates several 'convenient symlinks' to the bazel-bin/bazel-out directory within the workspace, containing several million files.Perhaps there are some things that we can improve to the IDE regardless, like fixing performance issues for cases like this: Regarding the Bazel feedback, there's not much we can address at the first impression, as the plugin is developed by Google. I collected it and added to the relevant tickets from our side, WSL support, CLion integration, and prioritization for context.Context. Maybe some of the problems listed above can be solved easily and I just haven't spend enough time figuring out a solution. 'context.' is a similar example - i would prefer to see the stdlib first in this case. For example, we (still) use ' /pkg/errors' for most projects, but when I type 'errors.' it lists some vendor folders first, followed by the stdlib and the package mentioned above is usually at the 6th place (or something similar). a way to configure the 'default' packages that are used for automatic imports would be fine. The 'typing' keymap is always the currently selected one, but the 'shortcut' keymap is always the one that is listed first, regardless of the selected one. On Linux the keyboard shortcuts in Goland behave rather strangely.

Goland bazel plugin install#

Working with Goland is rather difficult (the best way I found so far is to install an X server on the host, install Goland and all X libs on the wsl2 instance, configure xauth correctly and start the x server on the host and intellij within the instance).

Goland bazel plugin code#

Using VS Code in this setup is easy (just install VS Code on the host and type 'code' in the wsl2 instance). Goland does not seem to have any WSL2 support. As far as I understand, it's currently not possible to open a Go and C++ project in any single Jetbrains application (the C++ plugin for IntelliJ seems to be really old and unmaintained). For example, I wanted to use C++ for some parts (mostly computational stuff) alongside with Go/GRPC. it's hard to develop hybrid applications. Luckily it's possible to disable those symlinks in the bazelrc file. Opening a project with those folders nearly crashes Goland.

by default bazel creates several 'convenient symlinks' to the bazel-bin/bazel-out directory within the workspace, containing several million files. even with the plugin, bazel integration is rather bad - I have stopped using the plugin all together and rely purely on the command line This is rather unfortunate, because we also have a large Monorepo based on Bazel. the Bazel plugin is broken / not compatible with the current Goland version about 90% of the time. But for Go itself, I think Goland is currently the best choice. The later two are more popular for writing Ansible roles and other DevOps related tasks. Other popular editors are VS Code and vim. I really like Goland and nearly everyone at my company is using it now as main editor for Go development. Here is a short written feedback if you don't mind.