{"id":160270,"date":"2021-07-08T14:18:03","date_gmt":"2021-07-08T13:18:03","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=go&p=160270"},"modified":"2022-05-23T18:51:55","modified_gmt":"2022-05-23T17:51:55","slug":"goland-2021-2-reaches-beta","status":"publish","type":"go","link":"https:\/\/blog.jetbrains.com\/zh-hans\/go\/2021\/07\/08\/goland-2021-2-reaches-beta","title":{"rendered":"GoLand 2021.2 Reaches Beta!"},"content":{"rendered":"\n

GoLand 2021.2 Beta is out! This means that we have stopped adding new features and are now focusing on perfecting the release. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Beta version is quite stable in comparison to Early Access Program builds, but please keep in mind that there may still be some small issues with it. <\/p>\n\n\n\n

This is the last build in the EAP cycle that does not require a subscription. <\/p>\n\n\n\n

For this release, we focused on adding new features for Go modules. There is also a new option for formatting, support for Go 1.17 features, and support for generics in .go<\/em> files. We\u2019ve added new quick-fixes, including one that will help you to use the new \/\/go:build<\/code> syntax correctly.<\/p>\n\n\n\n

You\u2019ll find version control updates, including the ability to sign Git commits with GPG keys. There are also some UI improvements, such as a better view of attached projects. For web developers, pages will reload in the browsers when code is saved, and there is completion for MongoDB fields and operators. <\/p>\n\n\n\n

You can get the build via the Toolbox App<\/a>, download it from our website<\/a>, or use a snap package (for Ubuntu). You can also update from within GoLand. Just select Automatically check updates for Early Access Program<\/em> in Settings\/Preferences | Appearance & Behavior | System Settings | Updates<\/em>.<\/p>\n\n\n\n

Download GoLand 2021.2 Beta<\/a><\/p>\n\n\n\n

If you would like an interactive introduction to the new features in this GoLand release, the new What\u2019s New in GoLand 2021.2<\/em> course is available on the Learn GoLand<\/em> tab of the Welcome<\/em> screen. You\u2019ll also find our new Onboarding tour <\/em>there. It can help you quickly get acquainted with GoLand, and it will give you an overview of how to run and debug code and how to use the IDE\u2019s features.    <\/p>\n\n\n\n

Go Modules<\/h2>\n\n\n\n

Load go.mod changes manually<\/h3>\n\n\n\n

Previously, when you edited go.mod<\/em> files, GoLand would automatically run go list<\/em> commands after every modification. This obstructed the editing process, especially in large projects. <\/p>\n\n\n\n

You can now control this behavior. If you don\u2019t want GoLand to run go list<\/em> commands automatically, go to Preferences\/Settings | Build, Execution, Deployment | Build Tool<\/em>s, where you\u2019ll find the Reload project after changes in the build scripts<\/em> checkbox. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If you select the External changes<\/em> option, go list<\/em> commands won\u2019t be executed automatically when you edit files inside GoLand. You will instead see a Load Go modules Changes<\/em> icon, which you can click to load the changes when you are finished editing.  <\/p>\n\n\n\n

If you untick the Reload project after changes in the build scripts<\/em> checkbox, you will see the Load Go modules Changes<\/em> icon on all types of changes \u2013 both external and internal ones. <\/p>\n\n\n\n

We believe that there is no need to disable automatic reloading, but if you find it useful to do so, please get in touch with us. We would love to know more about your use cases.   <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Better support for different Go versions<\/h3>\n\n\n\n

If you use features from a version of the Go language that is newer than the one specified in your go.mod<\/em> file, you\u2019ll get an error, and GoLand will tell you what\u2019s wrong.<\/p>\n\n\n\n

For numeric literals and \/\/go:embed statements, a quick-fix is available that will change the Go version in go.mod<\/em>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Dealing with unused dependencies<\/h3>\n\n\n\n

There may be situations where you need to specify a module that isn\u2019t used anywhere in your code in a replace<\/em> directive. <\/p>\n\n\n\n

These unused dependencies used to be highlighted in red. Now, to help distinguish them from errors, they are highlighted in grey. If you hover over one of the grey lines, you will see an \u201cUnused dependency\u201d message.<\/p>\n\n\n\n

If you need to download the unused modules, press Alt + Enter<\/em> (\u2325 + ↩<\/em>) and choose the Download all modules to the module cache<\/em> option. You can also download individual modules. <\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Formatter<\/h2>\n\n\n\n

Go has the gofmt<\/em> tool for formatting your code, and GoLand also has its own formatter. <\/p>\n\n\n\n

There are various ways to enable \u201cgofmt\u201d<\/a> in GoLand, but users have regularly asked us to make enabling it more discoverable or to set it to be used by default. <\/p>\n\n\n\n

In this release, we have introduced the Run gofmt on code reformat<\/em> option. It\u2019s enabled by default and can be toggled in Preferences\/Settings | Editor | Code Style | Go<\/em>. <\/p>\n\n\n\n

When this option is checked, you can invoke both formatters with the shortcut Ctrl + Alt + L<\/em> (\u2318 + <\/em>\u2325 + <\/em>L<\/em>), and \u201cgofmt\u201d will be run after GoLand\u2019s formatter. This will apply both the user settings and the default style.<\/p>\n\n\n\n

This is just our first step towards making gofmt more discoverable. We have more changes planned.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Go 1.17<\/h2>\n\n\n\n

In Go 1.17 it will be possible to convert a slice to an array pointer<\/a>. GoLand will not mark these conversions as errors. To try out the Go 1.17 features, change GOROOT to \u201cGo 1.17beta1\u201d in Preferences\/Settings | Go<\/em>.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Generics a.k.a. type parameters<\/h2>\n\n\n\n

We\u2019ve been providing experimental support for generics since GoLand 2020.2. You can turn this feature on using the Enable generics (experimental support for type parameters)<\/em> setting in Settings\/Preferences | Go<\/em>. <\/p>\n\n\n\n

The experimental support for generics in GoLand used to only be available in files with the .go2 <\/em>extension. Now GoLand supports type parameters in .go<\/em> files, too. It no longer suggests renaming the file, but you will still need to enable support for generics in the settings or through a quick-fix. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

More quick-fixes <\/h2>\n\n\n\n

Support for the new \/\/go:build constraints formatting<\/h3>\n\n\n\n

Last year, the authors of Go suggested that \/\/+build<\/code> constraints syntax should be changed<\/a> to the new \/\/go:build<\/code> syntax.<\/p>\n\n\n\n

During this transition period, according to the new syntax, you can only place \/\/go:build<\/code> constraints at the top of the file. If you place them anywhere else in the file, GoLand will suggest a quick-fix that will move the \/\/go:build<\/code> lines to their proper location. <\/p>\n\n\n\n

In Go 1.16, you have to use the old syntax or both of them. We recommend getting used to the new one though. You can write \/\/go:build<\/code> lines, and if there are no \/\/+build<\/code> lines, GoLand will suggest a quick-fix that generates them.  <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Enable cgo support with one click <\/h3>\n\n\n\n

If you imported the \u201cC\u201d package but forgot to enable cgo <\/em>support in the project settings, the IDE will display a banner with the Enable cgo support<\/em> quick-fix.  <\/p>\n\n\n\n

There is also the Navigate to cgo import<\/em> option, which will put the cursor at the beginning of the package\u2019s name. This can help you find the import<\/em> statement in a big project. <\/p>\n\n\n\n

There is also the option to Edit Go project settings,<\/em> which opens a window with the settings for Build Tags and Vendoring<\/em>, and you can enable cgo<\/em> support, among other things. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Debugger<\/h2>\n\n\n\n

Preview mode<\/a> now works when you debug your application. It lets you open files successively in one tab. This helps you avoid cluttering the editor with multiple open files in separate tabs. <\/p>\n\n\n\n

To enable preview mode during debugging, go to Preferences\/Settings | Editor | General | Editor Tabs<\/em> and tick the Enable preview tab<\/em> checkbox. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Quick navigation<\/h2>\n\n\n\n

Starting with this release, you can Navigate to implementations<\/em> of the interfaces contained in the internal<\/em> folder. Click on the gutter to jump to the implementations. You can also jump back to the interface from its implementations.  <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

VCS updates <\/h2>\n\n\n\n

GPG signature<\/h3>\n\n\n\n

You can sign your commits with a GPG key to secure them. This feature can be enabled via Preferences\/Settings | Version Control | Git<\/em>. If this is your first time using a GPG key, you\u2019ll need first to configure it<\/a>. With an existing preconfigured GPG key, you just need to select it from the drop-down list. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

New options in pre-commit checks<\/h3>\n\n\n\n

You can now Run tests<\/em> and Analyze code<\/em> before committing your changes. Go to Preferences\/Settings | Version Control | Commit | Before commit <\/em>or click on the gear icon in the Commit<\/em> view. <\/em>GoLand will show the progress and the results of pre-commit checks in the Commit<\/em> area without opening additional modal windows. Please be aware that the Run tests<\/em> option is only available if you tick the Use non-modal commit interface<\/em> box in Preferences\/Settings | Version Control | Commit<\/em>. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

New search field in Local history menu<\/h3>\n\n\n\n

We\u2019ve improved the Local History<\/em> menu, which helps you track changes independently of version control. We\u2019ve added a new search field to it to help you to quickly find the text you are looking for in your Local History<\/em> revisions. To try it out, right-click on the file and go to Local History | Show History<\/em>. Please note that Local History<\/em> shouldn\u2019t be used as a substitution for VCS. We recommend making VCS your default choice for tracking changes and using Local History<\/em> as a last resort.  <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Changelists renamed<\/h3>\n\n\n\n

GoLand has been using \u201cDefault Changelist\u201d as the name for the node that stores all uncommitted changes. We\u2019ve made the phrasing more precise by using the word \u201cChanges\u201d instead of \u201cDefault <\/em>Changelist\u201d. This update will be available by default in your new projects. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The IDE will no longer add changelists automatically for Git operations. So, for example, a cherry-pick won\u2019t trigger the creation of a changelist. <\/p>\n\n\n\n

If you prefer automatic changelist creation, you can activate it in Preferences\/Settings | Version Control<\/em> by ticking the Create changelists automatically <\/em>checkbox.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

UI improvements <\/h2>\n\n\n\n

Clearer understanding of Go and GOPATH projects on the Welcome screen<\/h3>\n\n\n\n

As GOPATH-based projects are becoming less and less popular, the way projects were previously named is no longer suitable. We\u2019ve made the Go project the default for Go modules and renamed GOPATH-based projects to Go (GOPATH).<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Better view of attached projects <\/h3>\n\n\n\n

Previously, when you attached projects, they would be represented in the Project <\/em>view as child directories of the existing project. We decided to change that because the actual location of these projects on your computer could be very different from what was shown in GoLand. Attached projects will now appear in the Project <\/em>view as separate directories.   <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Advanced settings and navigation arrows<\/h3>\n\n\n\n

We\u2019ve added a new Advanced Settings <\/em>node <\/em>to Preferences\/Settings<\/em>. It contains additional configuration options, allowing you to, for example, configure a left margin for Distraction-free<\/em> mode. <\/p>\n\n\n\n

There is also a new navigation option in Preferences\/Settings<\/em>. You can now navigate back and forth between sections using the arrows in the top right corner of the window. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Update notifications from the Toolbox App<\/h3>\n\n\n\n

With this feature, you won\u2019t miss any important updates from our Toolbox App. GoLand will inform you when a new version is available and give you the option to update to the new version right from the IDE. You need to have Toolbox App version 1.20.8804 or later for this.    <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

New terminal options<\/h3>\n\n\n\n

You can change the cursor shape in the built-in terminal to underline <\/em>or vertical<\/em> by going to Preferences\/Settings | Tools | Terminal<\/em>.<\/p>\n\n\n\n

There is also a new option in the Terminal <\/em>settings: we now support the Use Option as Meta key <\/em>option. The Meta key temporarily modifies the normal action of another key when they are pressed together. Using the Meta key will help if you use the terminal a lot.<\/p>\n\n\n\n

For instance, you can now use the following shortcuts to cut down on the time you spend navigating through the terminal: <\/p>\n\n\n\n