Go to the next level with GoLand 2018.2

Today we are happy to announce that GoLand 2018.2 is released!

This major summer update has many goodies inside: support for Go modules out of the box (formerly known as vgo), an enhanced Move refactoring, new quick-fixes, additions to the Postfix Completion and Intention Actions families, and an upgraded debugger. The release makes working with VCS better across the board, and incorporates many other features from the latest IntelliJ Platform release such as frontend-related updates and Touch Bar support.

800x400_blog@2x

Click here to download GoLand 2018.2, or read on for the release highlights.

  • Integration with go modules (vgo) out of the box.
  • The Move refactoring gets a new dialog which shows whether an identifier is needed, and an ability to move symbols across packages.
  • A new quick-fix called Convert to expected type converts a value to the desired type whenever the language permits.
  • A new Implement missing methods quick-fix lets you quickly add missing methods if the expected type is an interface.
  • Implement Methods is now able to not only add methods from an interface to a chosen type, but also create this type right away.
  • New Intention Actions:

    • Add dot import alias lets you quickly add the dot alias to an import which makes all exported symbols available without a qualifier. Conversely, Remove dot import alias helps switch back to using the package name.
    • Introduce local variable helps add variables for function/method calls that return values.
  • New Postfix completion templates:

    • The .sort template transforms array or slice expressions and prepends them with an applicable sort method based on the element type.
    • The .rr template combines the power of two already available templates, .rre and .rrv.
  • There’s a new option to disable leading spaces for annotations that start with certain prefixes: Add leading space to comment in Settings | Editor | Code Style | Go | Other.
  • The debugger supports non-suspending breakpoints and lazy-loading for arrays, maps, and slices; supports deep nesting in maps; and offers a better presentation of key-value pairs in maps and slices.
  • Tools:

    • File watchers stores the configured File Watchers in the IDE settings and allows you to share them among different projects using the Project and Global options.
    • The Docker plugin now recognizes several new runtime command line options in the run configuration and adds an option to specify the base directory for executing a Docker build command for a dockerfile.
  • Version control system:

    • A new Merge Conflicts node groups files with merge conflicts for each changelist, making it much easier to find them.
    • Many improvements for the Log tab.
    • New option to skip the Push dialog for Git.
    • Support for multiple GitHub accounts.
  • User Interface:

    • Touch Bar support.
    • New option: Use dark window headers.
    • New icons on the IDE toolbar and tool windows.
  • JavaScript & TypeScript:

    • Support for TypeScript 2.9 and the upcoming TypeScript 3.0 releases.
    • New intentions: Implement interface, Create derived class, Implement members of an interface or abstract class, Generate cases for ‘switch’, and Iterate with ‘for..of’.
    • Find any unused code in your project with the new Code Coverage feature.

To take a closer look at all the new features, please visit the What’s New page.

If you have an active subscription to GoLand or the All Products Pack, feel free to upgrade to GoLand 2018.2 right away using the download page or the Toolbox App.

If you don’t, here is a free 30-day trial to give it a spin!

This entry was posted in New Features, Releases and tagged . Bookmark the permalink.

18 Responses to Go to the next level with GoLand 2018.2

  1. Tim says:

    I’m getting low memory warnings and hanging on OSX after upgrading from 2018.1

    • Florin Pățan says:

      Hi. Sorry to hear you have issues with the latest update. Please go to Help | Compress Logs and Show in… and either open an issue at our tracker https://youtrack.jetbrains.com/issues/Go or send them by mail to florin at jetbrains. Thank you.

      • Tim says:

        Thanks for offer of help but I found the problem. Our build process generates temporary files that includes a link back to the project directory, creating an infinite file system loop that GoLand chokes on.

  2. Yurina Shirahane says:

    How can I enable “Make project automatically” in Compiler settings and display “Problems Tool Window” in Goland as your help webpage wrote?
    https://www.jetbrains.com/help/go/problems-tool-window.html

  3. Maksim says:

    2018.2 is totally unusable when working with autogenerated code from proto-files (pb.go), it simply doesn’t render them. When you open pb.go file you see a content from the previous file, and nothing helps. Sometimes a blinking cursor is rendered, and that’s all. All other files (including original .ptoro) are rendered fine. Rolled back to 2018.1.

    • Ekaterina Zharova says:

      Maksim,

      Sorry for the inconvenience. Please, follow this issue for the updates: https://youtrack.jetbrains.com/issue/GO-5997
      Also, would you be so kind to add a piece of code to the request?

      • Maksim says:

        Maybe next time I’ll try to research a bit and provide more details, but now I have to work, so I rolled back to 2018.1.5, sorry.

        • Florin Pățan says:

          Maksim, totally understood. But maybe there’s something you can still help us with.

          You can have both 2018.1 and 2018.2 installed side by side.
          If you could install 2018.2 one more time and then open any project, go to “Help | Compress Logs and Show in….” and send us the zip archive with the logs, that would possibly help identify what’s wrong.

          And a description of the steps needed to reproduce the problem would also be helpful.

          Thank you in advance and sorry for the trouble caused.

  4. Raviraj Joshi says:

    With GoLand 2018.2, I’m constantly getting out of memory issues.

    • Florin Pățan says:

      Hi Raviraj, sorry to hear you have issues with the latest update. Please go to “Help | Compress Logs and Show in…” and then either send them via an issue on the tracker, https://youtrack.jetbrains.com/issues/Go, or by mail to florin at jetbrains and we’ll look into it as soon as possible.

      Thank you for your help and my apologies for the inconvenience this causes to you.

  5. asdfdsfsdf says:

    The worst release so far: debugging is buggy, editor is buggy (Ctrl+S were moving me to certain line in a file, restart fixed it), etc.

    • Florin Pățan says:

      I’m sorry you are experiencing issues with the build.
      Unfortunately based on the above description we cannot reproduce the errors.

      Please consider opening an issue on our bug tracker, https://youtrack.jetbrains.com/issues/Go, or sending me an e-mail at florin at jetbrains so we can investigate this.

      Providing steps to reproduce the issues, possibly sample code or video of the issues, as well as the IDE log files via “Help | Compress Logs and Show in…” will greatly help us figure out what’s going on.

      Thank you for your help.

  6. Seth Thompson says:

    Anyone notice that debug mode never completes successfuly?
    If I try to debug a test, I see the test pass, but debug mode always ends with

    Debugger finished with exit code 130 (interrupted by signal 2: SIGINT)

    the icon for test success is never green after debug mode it is always red/yellow

    I’m also having the issue where I cannot step. If I have a breakpoint, and either step into or over, it just runs to the next breakpoint.

    I’m using
    GoLand 2018.2
    Build #GO-182.3684.99, built on July 24, 2018
    Licensed to GoLand Evaluator
    Expiration date: August 24, 2018
    JRE: 1.8.0_152-release-1248-b8 x86_64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
    macOS 10.13.6

    and Go 1.10.3 darwin/amd64

  7. Hu Jianxin says:

    Hi, I play around a while with new goland, and have a quesiton. why the vgo project must be in $GOPATH/src dir?

    • Ekaterina Zharova says:

      Hello,

      Could you please add more details? It’s not required for vgo project to be in $GOPATH/src.

Leave a Reply

Your email address will not be published. Required fields are marked *