GoLand 2022.1 Help

Code style

If certain coding guidelines exist in a company, one has to follow these guidelines when creating source code. GoLand helps you maintain the required code style.

The IDE comes with two pre-defined schemes: the Project scheme and the Default scheme.

  • In the Project scheme, the settings that you configure apply only to your current project.

    These settings are stored in the codeStyles folder under .idea and are shared through VCS together with the project.

    The IDE creates the folder after you modify code style settings for your project.

  • In the Default scheme (IDE-level scheme), the settings that you configure apply to all existing projects that have the Default code style scheme selected.

    These settings are stored in the codestyles folder under the GoLand configuration directory and are not shared through VCS.

If you want to use the project code style scheme as your default scheme, you can copy it to the IDE level. The other way around is also possible: you can overwrite your current project settings with the settings from an IDE-level scheme and share them with other members of your team.

Configure schemes

In GoLand, code style settings are language-specific, so you need to configure them for every language that you use in your project separately. You can also copy the settings from one language and apply them to another language.

Configure code style for a language

  1. Press Ctrl+Alt+S to open the IDE settings and select Editor | Code Style.

    To configure a scheme for new projects, go to File | New Projects Setup | Settings/Preferences for New Projects | Editor | Code Style.

  2. Select the language for which you want to configure the code style.

  3. Select the code style Scheme that you want to configure: the Project scheme or one of the IDE-level schemes.

  4. Browse through the tabs and configure code style preferences.

    Use the right-hand section of the dialog to preview the changes. When you change a setting, one or several blinking areas appear in the preview area emphasizing the changes.

Disable code formatting in a scope

  1. In Settings/Preferences Ctrl+Alt+S, select Editor | Code Style.

  2. Click Formatter Control.

  3. Ensure that you selected a right scheme in the Scheme list.

  4. In the Do not format, optimize imports, arrange code pane, Click Add.

  5. In the Scopes dialog, click Add and select a scope. Select Local if the scope is intended for a personal use only. If you plan to share settings with team members, select Shared.

  6. Click OK.

  7. In the project tree, select the folder where you want to disable formatting and click Include.

  8. Click OK.

Disable code formatting in a scope

Apply code style from another language

For most of the supported languages, you can copy code style settings from other languages or frameworks.

  1. Press Ctrl+Alt+S to open the IDE settings and select Editor | Code Style.

    To configure a scheme for new projects, go to File | New Projects Setup | Settings/Preferences for New Projects | Editor | Code Style.

  2. Select the language for which you want to configure the code style.

  3. Select the code style Scheme that you want to modify: the Project scheme or one of the IDE-level schemes.

  4. From the list that appears, select the language to copy the code style from.

Manage code style on a directory level with EditorConfig

GoLand allows you to manage all code style settings for each individual set of files with EditorConfig support (enabled by default in the Settings/Preferences dialog (Ctrl+Alt+S)). All you need to do is place an .editorconfig file in the root directory containing the files whose code style you want to define. You can have as many .editorconfig files within a project as needed, so you can specify different styles for different modules.

All options from the .editorconfig file are applied to the directory where it resides as well as all of its sub-directories on top of the current project code style. If anything is not defined in .editorconfig, it's taken from the project settings.

All options in the .editorconfig file are divided into the following categories:

  • Standard options such as indent_size, indent_style, and so on. These options do not have any domain specific prefixes.

  • Generic IntelliJ options that have the ij_ prefix and are applicable to all languages:

    • ij_visual_guides

    • ij_formatter_off_tag

    • ij_formatter_on_tag

    • ij_formatter_tags_enabled

    • ij_wrap_on_typing

    • ij_continuation_indent_size

    • ij_smart_tabs

  • Common IntelliJ options supported by many (but not all) languages. They start with the ij_any prefix, for example, ij_any_brace_style.

  • IntelliJ language-specific options starting with the ij_<lang>_ prefix where <lang> is the language domain ID (normally a low-case language name), for example, ij_java_blank_lines_after_imports.

Add an .editorconfig file

  1. In the Project view, right-click a source directory containing the files whose code style you want to define and choose New | EditorConfig from the context menu.

  2. Select the properties that you want to define so that GoLand creates stubs for them, or leave all checkboxes empty to add the required properties manually.

  3. To preview how changes to your code style settings will impact the actual source files, click the eye icon in the gutter of the .editorconfig file and select a source file affected by it. The preview will open on the right.

    You can make changes in the preview pane to try and test how your configuration changes are reflected without worrying about making unwanted changes to the source code: all these changes are discarded when you close the .editorconfig file.

Productivity tips

Wrap call arguments, function parameters, and composite literal elements

  • To configure wrapping for call arguments, function parameters, and composite literal elements, open settings by pressing Ctrl+Alt+S and navigate to Editor | Code Style | Go | Wrapping and Braces.

    Code formatting: wrapping for call arguments, function parameters, and composite literal elements

Wrap arguments by using intention actions

  • To wrap arguments in the function signature, place the caret before the opening bracket, call the intention action by pressing Alt+Enter, and select Put arguments on separate lines. To revert this action, press Alt+Enter and select Put arguments on one line.

    Intention actions for wrapping arguments
Last modified: 13 May 2022