PhpStorm 2017.2 EAP 172.2465 : New Composer actions, traits improvements, new options for blank lines

Posted on by Anna Lebedeva

The new PhpStorm 2017.2 EAP build (172.2465.7) is now available! You can download it here or via JetBrains Toolbox App. Or, if you have the previous PhpStorm 2017.2 EAP build (172.2273) installed, you should soon get a notification in the IDE about a patch update.

This build delivers new features, bug fixes and improvements for PHP and the Web, and takes on the latest improvements in IntelliJ Platform.

New Composer actions: update, install and self-update

In this build, we’ve added new actions to Composer functionality in PhpStorm. Now you can execute the actions Update Dependencies, Install Dependencies, and Composer self-update directly from the IDE without the need to switch to the command line.

PhpStorm supports multiple composer.json files. Just right click on the composer.json in the Project view and use Composer actions in the context menu. If you open composer.json in the editor, you can access the same Composer actions by right-clicking inside the editor. In contrast, Tools|Composer uses the main composer.json configured in Settings|PHP|Composer.

composer

New Formatter options for blank lines

We’ve extended formatting options for blank lines to make it even more flexible for you. New options include Keep maximum blank lines before }, Keep maximum blank lines after {, and Minimum blank lines after a function. All the options can be found in Settings|Editor|Code Style|PHP|Blank Lines.

Screen Shot 2017-05-24 at 16.10.03

Unified Test Frameworks settings

We continue our effort in PHP settings simplification and unification. This build unites PHP Test Frameworks settings. Now PHPUnit, Behat, PHPSpec, and Codeception testing frameworks have a single settings page.

testing

Other features worth noting::

  • Method from class using nested trait is found inside trait: WI-30844

From platform side the update brings:

  • Breadcrumbs placement setting (Settings|Editor|General|Breadcrumbs)
  • Move Symbol Refactoring for JavaScript and TypeScript: more details

See the full list of bug-fixes and improvements in our issue tracker and the complete release notes.

Download PhpStorm 2017. 2 EAP 172.2465 for your platform from the project EAP page or click “Update” in your JetBrains Toolbox App and please do report any bugs and feature request to our Issue Tracker.

Your JetBrains PhpStorm Team
The Drive to Develop

Comments below can no longer be edited.

9 Responses to PhpStorm 2017.2 EAP 172.2465 : New Composer actions, traits improvements, new options for blank lines

  1. John Doe says:

    May 24, 2017

    Would be nice if we could get a setting for the number of spaces used within PHP docblock @params. So you can have “@param..type..$var..description” where dots are spaces. This lines up @param with @return.

    Currently no matter the setting if it’s manually written as above a reformat turns the second and third double spaces into a single space (though oddly it leaves the first space as a double).

    • Prashank says:

      May 24, 2017

      Yes please!!!

      • instagram images says:

        May 26, 2017

        We’ve extended formatting options for blank lines to make it even more flexible for you. New options include Keep maximum blank lines before }, Keep maximum blank lines after {, and Minimum blank lines after a function. All the options can be found in Settings|Editor|Code Style|PHP|Blank Lines.

    • Maxim Kolmakov says:

      May 25, 2017

      Please vote: https://youtrack.jetbrains.com/issue/WI-24129

  2. Adam Culp says:

    May 26, 2017

    The Tools->Composer option only seems to be present when the composer.json file is focused on. If any other file within the project is selected the Tools->Composer option is not present. Bug?

  3. Tino says:

    May 26, 2017

    For the last two EAP versions a couple of classes are marked as “undefined”. Nothing changed code wise and for the stable phpstorm version everything seems fine. Anybody else having these issues?

    • Tino says:

      May 26, 2017

      Completely invalidated cache which seems to fix this issue

Subscribe

Subscribe for updates