What's New in GoLand

When you open a project, GoLand indexes the files and runs the go list command, which reports information about the project structure. Indexing is paused while go list is running, and you don’t have access to code insight features until indexing is finished.

Previously, GoLand would run go list twice in some cases. We’ve changed our API and reduced the number of go list launches. We hope that this change significantly improves performance for large projects with many modules.

In the New context menu, you’ll now find the Go Workspace File action. When you select it, a go.work file will appear in your root folder. Existing Go modules will automatically be added to the go.work file.

You can now generate go.work from go.mod if you have replace directives there. Place the caret on a replace directive, press Alt+Enter to see all available intention actions, and select the Add … module to workspace quick-fix.

We've added references to doc links in GoLand. Clicking on them leads to the referenced element, while clicking on a text link leads to a text-link definition.

Both text and doc links are rendered as links in the Quick Documentation popup and the Documentation tool window.

Starting from Go 1.19, a heading is a line that begins with a number sign (#) followed by a space and the heading text.

New headings are rendered as HTML headings in GoLand's Quick Documentation popup and the Documentation tool window.

Lists are rendered as HTML lists in GoLand's Quick Documentation popup and the Documentation tool window.

If your type contains itself, you will get an "Invalid recursive type" error. To avoid this, you should include a pointer to a type, not a type itself. We now have a quick-fix for that.

GoLand now automatically picks up system variables related to Go modules and displays them in the Environment variables dialog window. To open this window, go to Settings | Go | Go Modules and click on the Edit environment variables icon.

The IDE now always shows package names in the Quick documentation popup for top-level declarations. Previously, package headers were shown only when doc.go or <pkg_name>.go files were found.

GoLand now supports connections to Docker that run in Windows Subsystem for Linux (WSL). You can set up such a connection in Settings | Build, Execution, Deployment | Docker.

There is now an easy way to pull a required image without running it from a Dockerfile or docker-compose.yml. For this, call up the context actions (Alt+Enter) on the highlighted image name and then select Pull Docker image.

We've introduced full support for .dockerignore files, including code highlighting and completion. These files are now taken into account when you build an image from the IDE.

Here documents allow you to redirect subsequent Dockerfile lines to the input of the RUN or COPY commands. GoLand now supports this syntax, so you can use it to generate config files or multiline scripts right in your Dockerfile files.

You can now set up additional Docker connections using Docker Contexts if you already have these settings in your Docker config. You can do so by calling the Add Service context menu in the Services view and selecting Docker Connections From Docker Contexts.

A preliminary iteration of long-awaited support for Redis has been implemented.

Now, when using quick search, you also have the ability to filter objects. All non-matching objects will be hidden.

This version introduces the new Code Vision feature for web development. It gathers various metrics for types and type members in your JavaScript and TypeScript code and displays this information near their declarations.

There's a new quick-fix to suppress inspections with a comment in YAML files, including Kubernetes files, OpenAPI specifications, and docker-compose.yml files.

We've also introduced an option to fold multiline comments that make up a block of 3 or more lines and start with #.