PHP Annotated Monthly collects all the interesting articles from the month in one convenient place. Collected and curated by Gary Hockin, Developer Advocate for PhpStorm.
The new PhpStorm 2017.3 EAP build (173.3531.17) is now available! You can download it here or via JetBrains Toolbox App. Or, if you have the previous PhpStorm 2017.3 EAP build (173.3415.21) 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 includes the latest improvements in IntelliJ Platform.
Reorganized PHP Code Style settings page
PhpStorm has a lot of different Code Style options and it’s not always easy to find them. To simplify the task, we’ve reorganized PHP Code Style page by adding new tabs – Code Conversion and Code Generation and moving all options from Other tab to the corresponding pages.
Since Blank line before return has been moved to Blank Lines tab for consistency and now allows integer instead of true/false values the setting won’t be migrated for EAP to EAP upgrade and should be changed manually. For Release to EAP upgrade, all settings should be migrated.
Apart from new features, this build has many bug fixes, including this:
- Invalid descendent file name “ssh:” or directory a\b (on Linux) (WI-2449)
See the full list of bug-fixes and improvements in our issue tracker and the complete release notes.
Download PhpStorm 2017.3 EAP 173.3531 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
PhpStorm supports all the major PHP testing frameworks: PHPUnit, Codeception, Behat, and PHPSpec.
Recently we’ve published a series of short videos about running PHPUnit and Codeception tests in PhpStorm. The videos guide you through the PHPUnit and Codeception setup process and show you how to work with test results.
This process is generally the same whichever testing framework or PHP interpreter you choose. First, configure a PHP interpreter. Second, configure the testing framework. Third, create a dedicated run configuration for the selected test framework, and finally run it.