// composer.json { "require": { "php": ">=5.3.9, <7.3.0", "symfony/symfony": "2.8.*", // v2.8.15 "doctrine/orm": "^2.4.8", // v2.4.8 "doctrine/dbal": "<2.5", // v2.4.5 "doctrine/doctrine-bundle": "~1.4", // 1.6.4 "symfony/assetic-bundle": "~2.3", // v2.8.1 "symfony/swiftmailer-bundle": "~2.3,>=2.3.

One project I’m working on has multiple separate parts in different git repositories that are brought into the main project using linked composer directories. I needed to get step debugging working in PhpStorm and this is the approach I took.

Any JetBrains IDE has an amazing feature that can significantly improve your development experience; whether it's PhpStorm, WebStorm, IntelliJ IDEA, PyCharm, or any other project; this feature enables better search and allows for custom file colours.

If you are like me and have been programming for a bit, you probably have worked with several editors and IDEs. Over the years, I have tried a bunch of them - with varying degrees of successes.

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.

Configuring PhpStorm correctly is important to get the most out of your IDE, and PhpStorm 2017.2 has made it easier by allowing you to detect some of the settings from your `composer.json` file.