Run Targets are a new IDE feature that allows you to run code in environments where GoLand is not installed.

How to use: If a target already exists, select it from the Run on field in a Run Configuration, then run that configuration.

If not targets exist, then click on Manage Targets, next to the Run on field.

Then, click + (macOS) / Plus (Windows/Linux) and select in which environment you want to run the application or test.

After the IDE introspects that environment, click on Next, confirm the environment settings, and click OK.

Then select the newly created target in the Run on field.

Configure any additional options, and, finally, run the configuration as with any other.

Pro tip: If you want to compile your sources in a remote environment, then select the Build on remote environment option from the Run Configuration settings.

Pro tip: You choose to compile on the local machine. This means you don't have to worry about the dependencies being available in that environment.

Go 1.16 introduced a new feature called go:embed.

This works using a compiler directive, //go:embed, and a variable, or more, of type string, []byte, or embed.FS.

If you want to embed a directory, then you must use the embed.FS type for the variable in which you need to embed the content.

How to use: You don't need to do anything special to get the IDE to support this feature.

Open any Go 1.16, or newer, based project, and embed what you need.

Calling *t/b.Fatal** methods from a goroutine is not advised as it may produce unexpected behavior.

How to use: You don't need to do anything to run this inspection as it's enabled by default.

Open your tests or benchmarks and see if it catches any issues.

If you need to add keys to existing struct types, you can now do this quicker using the dedicated Add key to tags feature.

How to use: Place the cursor on a struct type, then press ⌃⏎ (macOS) / Ctrl+Enter (Windows/Linux).

From the Context Actions menu, select Add key to tags, and start typing the key name.

Need to change the case of struct tag keys?

Choose between snake_case, (lower) camelCase, (upper) CamelCase, or kebap-case and apply this to the whole struct in a few steps.

How to use:

Place the cursor on a struct field, then invoke the Context Actions menu via ⌃⏎ (macOS) / Ctrl+Enter (Windows/Linux).

Select Change field name style in tags, and choose between one of the four styles available.

How to use: Copy your JSON data in the clipboard then paste it in an empty place in your code.

When the IDE asks you about converting the JSON to a Go type, press Yes and finish the action by giving the new type a name.

How to use: Copy a part of the JSON data in the clipboard then paste it inside an existing struct tag.

When the IDE asks you about converting the JSON to a Go type, press Yes and you are done with .

How to use: Press ⌘⌥⏎ (macOS) / Ctrl+Alt+Enter (Windows/Linux) on function call that returns an error and select Handle error.

How to use: Place the cursor on a type that's not yet defined but used.

Then, press ⌥⏎ (macOS) / Alt+Enter (Windows/Linux) and select the Create type action.

A type will be created. It will include all the fields too.

Do you need to access your struct fields via getters and setters? Add all the boilerplate code you need using the dedicated Generate getter and setter action.

How to use: Select a struct type, then press ⌥⏎ (macOS) / Alt+Enter (Windows/Linux) and choose Generate getter and setter from the list of available actions.

Choose which fields should have these methods generated, then press OK to generate them.

Choose the receiver name and receiver type then continue working on your code as usual.

Pro tip: You can choose either all fields, or select the individual fields that need to have these methods generated.

If you have an anonymous type defined, you can extract it into a standalone type and reuse it across your code.

How to use: Invoke Refactor this with ^T (macOS) / Ctrl+Alt+Shift+T (Windows/Linux), on the anonymous type, then select the Extract type from the list of available refactorings.

Give it a name and start reusing the newly created type in your code.

If you need to change your Go module's name or upgrade it to a new major, then the Rename refactoring has you covered.

How to use: Place the cursor under the module name in the go.mod file, then invoke the Refactor this feature, ^T (macOS) / Ctrl+Alt+Shift+T (Windows/Linux).

Select Rename from the list and change the module according to your needs.

Pro tip: You can preview the changes by clicking on the Preview button in the dialog or undo them with Undo operation. You can also undo the change later using the Local history feature.

Pro tip: If you upgrade your module's import path to a new major version, don't forget to tag the release too.

How to use: Press . (dot) after the function/method call and continue to type the varCheckError, or simply vce, postfix completion.

It will surround your code with the appropriate boilerplate to create any missing variables that are returned and handle the error checking part for you.

How to use: Invoke the Basic Completion feature using ⌃␣ (macOS) / Ctrl+Space (Windows/Linux) after the FROM directive in a Dockerfile and let the IDE assist you with the name and tag of the image you want to use.

How to use: Create a file with .http extension in your project. Then, type the request you want to make.

Finally, press ⌃⏎ (macOS) / Ctrl+Enter (Windows/Linux) and use the Run "address" action from the menu.

How to use: Hover the cursor on the top right side of the IDE and click on the IDE icon next to the browsers ones.

An embedded browser tool window will show up. You can the make changes to the template file and have them show up in the IDE without having to switch to a standalone browser.

When you are done, close it like you would any other tool window.

Pro tip: Your IDE uses JCEF to display the page, which is based on the Chromium browser.

How to use: Press ⌥⏎ (macOS) / Alt+Enter (Windows/Linux) and select the Convert multidocument YAML to List or Convert List to multidocument YAML to change between formats.

Note: You must have the Kubernetes plugin provided by JetBrains installed for this action to work.

How to use: Click on the Run button in a Kubernetes resources definition file and select the Delete from Context "xyz" and Namespace "xyz" action to teardown those resources.

Note: You must have the Kubernetes plugin provided by JetBrains installed for this action to work.