{"id":21781,"date":"2020-06-22T13:22:18","date_gmt":"2020-06-22T13:22:18","guid":{"rendered":"https:\/\/blog.jetbrains.com\/phpstorm\/?p=15774"},"modified":"2020-07-14T16:55:44","modified_gmt":"2020-07-14T16:55:44","slug":"phpstorm-2020-2-eap-4","status":"publish","type":"phpstorm","link":"https:\/\/blog.jetbrains.com\/phpstorm\/2020\/06\/phpstorm-2020-2-eap-4\/","title":{"rendered":"PhpStorm 2020.2 EAP #4"},"content":{"rendered":"

The Early Access Program for PhpStorm 2020.2 is in full swing, and today we\u2019ve got Build 4 of the 2020.2 EAP for you.<\/p>\n

Read on to learn about the new control flow engine, the Add caret per selected line<\/em> action, and smart handling of terminal commands.<\/p>\n

If you prefer to watch rather than read, check out our EAP video series on the JetBrainsTV<\/a> YouTube channel. Episode 1<\/a> is already available.<\/p>\n

<\/i>Download PhpStorm 2020.2 EAP<\/a><\/p>\n

<\/p>\n

New control flow engine<\/h2>\n

PhpStorm 2020.2 introduces a new version of the control flow engine, which is now more powerful than ever. We\u2019ve already shown some improvements in the EAP#1 post<\/a>. Let\u2019s explore what it offers in more detail by looking at some scenarios from real-life projects.<\/p>\n

Condition always true<\/h3>\n

Let\u2019s start with the new Condition always true<\/em> inspection:<\/p>\n

\"always_true\"<\/p>\n

In this code snippet, PhpStorm understands that $item<\/code> must always have the type FOFTable<\/code>, as otherwise the function returns false<\/code>. As a result, is_object($item)<\/code> is always true, and the whole ternary operation can be simplified.
\nTo help you more easily understand what\u2019s going on, the inspection message provides detailed information about the cause. There is also a quick-fix that lets you navigate to the expression that uniquely defines the current value.
\nHere is another example of this inspection in action:<\/p>\n

\"always_true_2\"<\/p>\n

PhpStorm knows that as part of the elseif<\/code> chain, the case with $stubContent === null<\/code> has already been covered, so the last condition can be simplified.
\nThere are several other new inspections based on the new engine, including Expression is always \u2018null\u2019<\/em>, Result of \u2018instanceof\u2019 is always \u2018true\u2019, <\/em>and Variable is always true\/false when reached.<\/em> Let\u2019s look at them in more detail.<\/p>\n

Result of \u2018instanceof\u2019 is always \u2018true<\/h3>\n

Suppose we have the following non-trivial hierarchy:<\/p>\n

\"hierarchy\"<\/p>\n

Inside ConfigEntityBase<\/code>, we have the following code:<\/p>\n

\"always_true_3\"<\/p>\n

Because ConfigEntityBase<\/code> implements ThirdPartySettingsInterface<\/code>, the expression is always true. PhpStorm highlights it as redundant and displays a warning that suggests unwrapping the if<\/code> statement for clarity.<\/p>\n

Variable is always true\/false when reached<\/h3>\n

PhpStorm not only analyzes conditions but also tracks the values of variables. It can suggest increasing code readability by replacing the always true\/false variables with the corresponding boolean values.<\/p>\n

\"always_true_6\"<\/p>\n

In this example, the ternary operator makes sure that $empty<\/code> is always true in the first branch, so we can safely replace the variable with just the true<\/code> value.
\nThe inspection is disabled on purpose for the case below. This is because, according to our investigations, such code is often used to quickly change the default value:<\/p>\n

\"always_true_5\"<\/p>\n

Expression is always \u2018null\u2019<\/h3>\n

In addition to true\/false values, PhpStorm now also tracks the null value of the variable. Let\u2019s take a look at the Expression is always \u2018null\u2019<\/em> inspection.<\/p>\n

\"always_null\"<\/p>\n

In this example, PhpStorm builds the control flow and sees that the assigned null<\/code> value isn\u2019t rewritten, neither by a new assignment nor by a pass-by-reference call. The IDE highlights the usage of $default<\/code> and suggests simplifying the expression to make it more clear.<\/p>\n

Add caret per selected line\u00a0action<\/h2>\n

The new Add Caret Per Selected Line <\/em>action creates carets at the end of each selected line, and deselects the lines. Invoke it using the shortcut Alt+Shift+G<\/em> on Windows\/Linux or \u2325\u21e7G<\/em> on macOS.<\/p>\n

\"add_caret_action\"<\/p>\n

Smart handling of terminal commands<\/h2>\n

PhpStorm has many features that can help you do specific jobs faster. In the upcoming v2020.2, if you run certain commands from the built-in terminal, the IDE will now suggest using existing IDE features instead.
\nLet\u2019s say you want to check commit logs. If you type git<\/code> log<\/code> in the built-in terminal, the IDE will highlight the command in a different color, indicating that it can be handled by the IDE itself. Press Ctrl+Enter<\/em>, and the IDE will open the Git<\/em> tool window on the Log<\/em> tab so you can explore commit logs with less effort.<\/p>\n

\"terminal_smart_commands\"<\/p>\n

This is still a work in progress, so we\u2019d love to hear what other PHP-related commands you would like PhpStorm to handle in a similar fashion.
\nIf you don\u2019t find this feature useful in your workflow, you can disable smart commands by unchecking Smart command handling<\/em> in Preferences\/Settings | Tools | Terminal<\/em>.<\/p>\n

\n

The full list of changes, including bug-fixes and improvements, is available in the release notes<\/strong><\/a>.<\/p>\n