WebStorm 2020.1 EAP #7: Displaying Terminal Sessions Side by Side, and Updates to Introduce Field Refactoring and Commit Flow

Ekaterina Ryabukha

WebStorm 2020.1 EAP build #7 is now available!

If you’re unfamiliar with our Early Access Program or if you want to catch up on all the new features, check out our previous EAP blog posts.

The Toolbox App is the easiest way to get the EAP builds and keep both your stable WebStorm version and any EAP versions up to date. Or you can download the EAP builds from our website. You can also choose to be notified right from the IDE when a new EAP build is available: go to Preferences/Settings | Appearance & Behavior | System Settings | Updates and select Automatically check updates for Early Access Program.

DOWNLOAD WEBSTORM 2020.1 EAP

Important! WebStorm EAP builds are not fully tested and might be unstable.

Here are some of the highlights of WebStorm 2020.1 EAP #7 (build 201.6073.22). For the full list of issues fixed in this update, see the release notes.

Displaying terminal sessions side by side

WebStorm 2020.1 will make it easier for you to work with the built-in terminal emulator, as you can now split terminal sessions vertically and horizontally. This long-awaited functionality will let you keep an eye on the output of several tools that are currently in use without switching between tabs.

To try the new functionality out, right-click anywhere in the Terminal tool window area and select Split Vertically/Split Horizontally from the context menu.

split-terminal-sessions

If you no longer need to have several terminal sessions, you can right-click on the session you want to close and select Close Session from the context menu.

Reworked UI of the Introduce Field refactoring

When using the Introduce Field refactoring (Cmd/Ctrl-Alt-F) in WebStorm 2019.3, you had to make changes in a separate dialog, which would block you from working with code directly and wouldn’t let you see the applied changes as you typed.

introduce-field-refactoring-webstorm-2019-3

With the updated implementation of the Introduce Field refactoring available in WebStorm 2020.1, it will take fewer clicks to apply the refactoring, and you’ll be able to see a preview of changes in the context of the code you’re working with.

introduce-field-refactoring-webstorm-2020-1

We’re still looking for more ways to improve the current implementation of this refactoring, so please share your feedback on what you’d like to be changed in the comments below.

Changes to the commit flow

Many of you have given us feedback about the Commit tool window since we enabled it by default for all users in one of the 2020.1 EAP builds. Taking into account all the different opinions about the updated commit flow, both inside and outside JetBrains, we’ve changed its behavior. Here’s how.

The modal Commit dialog is enabled by default again, as it was in v2019.3 and earlier. The commit features look exactly like they used to before v2020.1. This way, we don’t break the fashion in which a lot of users are accustomed to committing things.

If you like the Commit tool window better, you can still turn it back on by going to Preferences/Settings | Version Control | Commit Dialog and ticking the Commit from local changes without showing the Commit dialog box. In the future, we’ll promote the new UI in the Commit dialog to allow in-place switching.

enabling-commit-from-local-changes

With that said, it’s worth mentioning that starting with v2020.1, all new users will still get the Commit tool window as the default way of committing changes. This means that if you start WebStorm on a clean machine without using any configs from previous builds, you’ll see the Commit tool window by default. You can, of course, get back to the modal Commit dialog by unchecking the option Commit from Local Changes without showing the Commit dialog, which was mentioned earlier.

Installing Git from the IDE

Starting with v2020.1, you’ll no longer need to download Git manually if it’s not yet installed on your machine. In particular, WebStorm will warn you that Git is not installed when you try to import a project from VCS by clicking Get from Version Control on the welcome screen. If it’s not there, the IDE will suggest downloading Git and set it up for you in the background.

Similarly, if you have a project that uses Git and the IDE fails to find the path to the Git executable, you’ll see the notification that suggests downloading and installing Git for you. However, you’ll probably want to check your path to Git in Preferences/Settings | Version Control | Git before downloading it once again.

Those are the most notable highlights. Please report any issues on our issue tracker. And stay tuned for next week’s update!

The WebStorm team

Comments below can no longer be edited.

12 Responses to WebStorm 2020.1 EAP #7: Displaying Terminal Sessions Side by Side, and Updates to Introduce Field Refactoring and Commit Flow

  1. Kino says:

    March 5, 2020

    Hello! Thanks for all this updates! Any idea when will it be shipped to stable? Can’t wait for it!!

    • Ekaterina Ryabukha says:

      March 5, 2020

      Hello,

      We’re happy to hear that you like the latest updates! The 2020.1 release is scheduled for the beginning of April, please stay tuned.

    • Kim Major says:

      March 5, 2020

      Since it’s possible to have the EAP and the stable running side-by-side, I never wait for the stable 🙂

  2. Keegan says:

    March 5, 2020

    Hi, Appreciate all the hard work but I feel like our concerns in https://youtrack.jetbrains.com/issue/IDEA-231847 have not really been addressed with the new commit tool window. Can we please have some response to this issue?

    • Ekaterina Ryabukha says:

      March 6, 2020

      Hello Keegan,

      It’s likely that these concerns will be addressed in the next release cycle as we still plan to work on improving the commit flow. Unfortunately, we cannot implement any major changes in the products in the current release cycle anymore as the release date is drawing near, and this change would be major. We’re sorry for any inconvenience it may be causing you.

    • Dmitriy Smirnov says:

      March 6, 2020

      If the new UI does not work well for you, please disable the Commit from Commit toolwindow option in Settings | Version Control | Commit dialog.

    • Keegan says:

      March 7, 2020

      Thanks Ekaterina and Dmitriy,
      As someone who really appreciated the tool window implementation from 2019.3.3, I find this change really disappointing as it was a huge improvement to my workflow. I have no idea why the decision was made to change it. Returning to the old commit dialog now feels like such a step backwards.

      I understand that further refinement on the new tool window is becoming out of scope for this release cycle, so I feel like reverting it to the version in 2019.3.3 and save it for 2020.2 would be the more appropriate thing to do, as this new one clearly is not ready for a production release.

      My understanding of the intent behind EAP releases is to allow for feedback from the community. Ignoring this feedback and shipping changes that negatively impact existing workflows is really unfortunate to see.

      I sincerely hope you reconsider your position.
      Thank you

      • Ekaterina Ryabukha says:

        March 10, 2020

        Thanks for sharing your thoughts on the commit flow.

        You’re right, the intent behind EAP releases is to collect feedback from the community. Unfortunately, the implementation from 2019.3.3 also has its own drawbacks, primarily related to the lack of space to show all the needed components in the bottom tool window. We hope that the new Commit tool window solves all the usability problems present in the 2019.3.3 implementation one day, however, there’s still a lot of refinement work to do.

        For now, we decided to keep the old modal commit dialog available by default as we don’t want to break the way in which a lot of users are accustomed to committing changes (most users still use it and it would negatively impact their existing workflows). Having two alternatives to it (the Commit tool window and the implementation from 2019.3.3) could be confusing to some users. We might reconsider our position, however, we can’t provide any guarantees at the moment. Please stay tuned and follow this issue for updates: https://youtrack.jetbrains.com/issue/IDEA-231132. Sorry for the inconvenience!

  3. Krystian says:

    March 9, 2020

    Webstorm team is doing a great job, but new UI for committing is worst in the latest version. Thank you for the “Commit from local changes without showing the Commit dialog” option, cause still, I will be able to use previous one 🙂

    • Ekaterina Ryabukha says:

      March 10, 2020

      Hello Krystian,

      Thanks for the feedback! I’ve shared it with the team responsible for the changes to the commit flow.

  4. David Gilbertson says:

    March 23, 2020

    Splitting terminal windows is excellent!

    A request: can we have the icons in the right click menu for split horizontally/vertically like we do for tabs? I get them mixed up and select the wrong one roughly 90% of the time 🙂

    Also, it’s a pity I’ll be losing the commit functionality that I like, now having to choose between the new tool window (that tries to cram side-by-side diff into an existing tab) and the old commit popup window. This is a real step back for WebStorm, fingers crossed this doesn’t make it into the final release.

    • Ekaterina Ryabukha says:

      March 23, 2020

      Hi David,

      Thank you for the feedback! I’ve created a new issue for adding icons to split vertically/horizontally actions, please follow it for updates: https://youtrack.jetbrains.com/issue/IDEA-235842. For now, I’d recommend right-clicking the name of the terminal tab, e.g. Local, instead. This way, you’ll see the icons next to each action and avoid confusion caused by lack of them.

      As for the commit flow, there’s a workaround that you can use to restore the layout from 2019.3.3, please see this issue: https://youtrack.jetbrains.com/issue/IDEA-231132. Feel free to share more thoughts on why you like the old commit flow better/what you’d improve in the new one in that issue or in the comment below, we’re still collecting user feedback.