{"id":23582,"date":"2020-06-11T17:21:41","date_gmt":"2020-06-11T17:21:41","guid":{"rendered":"https:\/\/blog.jetbrains.com\/webstorm\/?p=11232"},"modified":"2020-08-26T15:39:59","modified_gmt":"2020-08-26T15:39:59","slug":"webstorm-2020-2-eap-3","status":"publish","type":"webstorm","link":"https:\/\/blog.jetbrains.com\/zh-hans\/webstorm\/2020\/06\/webstorm-2020-2-eap-3","title":{"rendered":"WebStorm 2020.2 EAP #3: New Intentions for Loops, Support for Git Installed in WSL2, and More"},"content":{"rendered":"

WebStorm 2020.2 EAP build #3 is now available!<\/strong><\/p>\n

If you\u2019re 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<\/a>.<\/p>\n

The Toolbox App<\/a> is the easiest way to get the EAP builds and keep your stable WebStorm version and any EAP versions up to date. Or you can download the EAP builds from our website<\/a>. 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<\/em> and select Automatically check updates for Early Access Program<\/em>.<\/p>\n

DOWNLOAD WEBSTORM 2020.2 EAP<\/a><\/p>\n

Important! WebStorm EAP builds are not fully tested and might be unstable.<\/strong><\/p>\n

Here are some of the highlights of WebStorm 2020.2 EAP #3 (build 202.5428.27). For the full list of issues fixed in this update, see the release notes<\/a>.<\/p>\n

New intentions for loops<\/h2>\n

As usual, we\u2019ve added some new intentions that can help you do routine work a bit faster. This time, they are for loops. Just like with any other intention, the new ones can be invoked with\u00a0Alt+Enter.<\/em><\/p>\n

To begin with, WebStorm can now assist you with converting a traditional for<\/code> loop with a numeric index into the forEach<\/code> array method.<\/p>\n


\n\"convert-for-loop-to-for-each-method-call\"<\/p>\n

If you want to replace a for<\/code> loop with a for \u2026 of<\/code> statement, the IDE can help you with that too. To see the intention for that, place the caret on the for<\/code> keyword.<\/p>\n

\"convert-to-for-of-syntax\"<\/p>\n

Finally, you can now swiftly convert a .map()<\/code> array method to a separate variable declaration with a for \u2026 of<\/code> loop.<\/p>\n

\"convert-map-to-for-of-loop\"<\/p>\n

Support for Git installed in WSL2<\/h2>\n

As WSL is becoming an important part of the development process on Windows, we\u2019ve been working on adding support for all the necessary workflows to our IDEs. In the first<\/a> and second<\/a> bug-fix updates for WebStorm 2020.1, we fixed a lot of known Node.js-related issues with WSL. Now, we\u2019ve implemented the missing support for Git installed in WSL2.<\/p>\n

The IDE can switch between Git executables depending on the project location. When a project is opened from WSL (via the \\wsl$ path), the IDE will automatically switch to Git from WSL and provide you with the ability to use all the Git-related features.<\/p>\n

Please note that the upcoming WebStorm 2020.2 allows you to use Git only from WSL2, which is available in the May update of Windows 10, version 2004<\/a>. Unfortunately, the IDE won\u2019t support WSL1 because Git from WSL1 doesn\u2019t return output reliably when called from Windows. This could lead to incorrect results from Git commands (see IDEA-242469<\/a> and the corresponding WSL request<\/a> for more information).<\/p>\n

Experimental presentation of findings in Search Everywhere<\/h2>\n

Starting with this EAP build, all the findings in the Search Everywhere<\/em> popup (Shift+Shift<\/em>) will be shown in a slightly different way. Specifically, the search results are no longer grouped by type. Instead, they are grouped based on their relevance to the search query.<\/p>\n

\"search-everywhere-new-presentation-of-results\"<\/p>\n

This is an experimental feature and we want to hear your thoughts about it. If you realize that the old presentation of the search results works better for you, you can switch back to it by unchecking the search.everywhere.mixed.results<\/code> option in Experimental Features<\/em>. To access them, use Search Everywhere<\/em> or Find Action<\/em> (Cmd\/Ctrl+Shift+A<\/em>).<\/p>\n

That\u2019s it in terms of the biggest highlights. This build also comes with some smaller but still important changes, such as:<\/p>\n