GoLand 2018.1.3 Update is Here

Andrey Cheptsov

For a couple of weeks we’ve been rather busy addressing your feedback, and here’s an update to keep you in the loop with what exactly was done. Welcome GoLand 2018.1.3, a fresh update, that, though doesn’t bring noticeable Go-specific improvements, comes with lots of bug fixes and improvements related to the UI and JavaScript and SQL support.

The update is available via Toolbox App, or you can still install it the old way, by using the Check for Updates menu in GoLand itself, or (why not) just download a copy of installer our website.

Here’s the list of most interesting changes that come with this update:

  • For side-effects import statement, code completion now includes non-JavaScript files as well, e.g. CSS.
  • GoLand now displays the type inferred by Flow server as a part of Brief Info that pops up when hovering an expression holding Ctrl or Cmd
  • Angular 6 improvements along with integration with Angular CLI 6 blueprints
  • TypeScript code completion updated according to the TSLint rules
  • Flow support within Vue files
  • Find Usages on SQL files now includes the DDL Data Sources that use them
  • Support for .sqlite/.sqlite3 files
  • Run SQL Script action now available in the Database (on a data source or a scheme) and Project (on the file) tool windows. This action can be used to import data from SQL dump files.
  • Fixed Z-order of child windows that was broken in one of the earlier builds is broken no more.

For more a more detailed report, see the release note.

P.S. EAP for GoLand 2018.2 is around the corner, and it will bring lots of goodies, so stay tuned!

Happy developing!

Comments below can no longer be edited.

8 Responses to GoLand 2018.1.3 Update is Here

  1. Bill says:

    May 11, 2018

    i set auto upgrade goland in toolbox, so this afternoon, the toolbox just start auto download the the update files, after x secs later, it display an error msg said “Verification error. Downloaded file size mismatch.”, and repeat download again, and display an error, and repeat previous steps.

    something wrong in your cdn server?

    • Andrey Cheptsov says:

      May 11, 2018

      Could you please check the logs (by Toolbox App) and if possible file to the issue tracker or here?

  2. Fork says:

    May 12, 2018

    Yet again no update, only download. Your toolbox is a piece of junk, make built in updater that can update through versions.

    • Florin Pățan says:

      May 12, 2018


      Can you please help us understand how we can improve the toolbox? Where does it fall short for you? What would you like to see changed?

      Thank you.

      • Fork says:

        May 12, 2018

        I am using Linux (Ubuntu). We at Linux does not need your alien looking
        (and memory hungry as any Java app) “Toolbox” at all. We already have unified way of software updates.

        Take a look at how Google does it for their Chrome (DEB, I don’t know about how their RPM installation works):
        * there’s a script in a chrome DEB-package that adds link to their repository into `/etc/apt/sources.list.d/…`.
        * `apt` will check for updates after that.

        • Florin Pățan says:

          May 13, 2018

          Thank you for the feedback.

          The patch update issue was fixed, you can try now to upgrade if you wish to do so. Sorry for the inconvenience.

          As for the Toolbox, it is entirely optional and provides more functionality than just upgrading the IDE. You can manage your projects, test new IDE versions and rollback if you have any problems, all from a single place. Combined with the Chrome extension it also allows you to open GitHub repositories straight from the browser. And if the memory consumption is an issue, you can choose not to run it in the background.

          Speaking of Ubuntu/Linux, we also support snaps, see https://snapcraft.io/GoLand.

          If you have any other feedback, features you’d like to see in the IDE, improvements to existing ones, please let us know either here or on our issue tracker, https://youtrack.jetbrains.com/issues/Go

          • Aleksei says:

            May 13, 2018

            > And if the memory consumption is an issue, you can choose not to run it in the background.

            Actually, I wonder if there is a way for Toolbox to be ran as a “normal” application, with a foreground main window, not a tray icon pop-out panel. I.e. I’d click its icon on the taskbar/panel/dock (or desktop or whatever) and it would run, showing a normal window, just like any other app.

            I believe this would actually make Toolbox useful for opening projects, as the tray icon is different from the usual navigation flows. I mean, when I run almost every other app from the other places of the system UI, Toolbox tends to be forgotten (90% of time I run the IDE and open projects from there, wasting a few clicks and waiting for the wrong project to open) or just feels odd.

            If this is not available, please consider this as a feature request.

            As for the auto-updates – I have no idea how it works right now and what’s feasible (and what’s not), but just thinking about possibilities – the Toolbox could have an optional tiny background-running GUI-less component, light on system resources. Its sole purpose would be to check for updates and behave as appropriate, e.g. run the main app to perform the actual update or notify user or whatever.

          • Fork says:

            May 15, 2018


            > light on system resources.

            They are writing for JVM stack. This cannot be “light on system resources”


Subscribe for updates