PHP Code Sniffer and PHP Mess Detector are the proven tools for ensuring that your code is clean, consistent, and conforming to the chosen coding standards. In PhpStorm 2018.2, we've simplified setting up of these tools to the point that almost no setup is actually required. The paths to Code Sniffer and Mess Detector are now automatically detected from composer.json – in the same way as it happens for PHPUnit or Behat. (more…)

Every PhpStorm release brings new inspections among other features, and PhpStorm 2018.2 is no exception. The new inspections will detect extensions that are not listed in composer.json, highlight the non-canonical order of elements in PHPDoc annotations, and warn you when an optional parameter is used in a method declaration before the required one. Let's take look at them in more detail. (more…)

In PhpStorm 2017.3, we’ve implemented several inspections that will help you eliminate unhandled exceptions and redundant @throws from your code. Initially, it was possible to exclude the \RuntimeException and \LogicException exceptions, as well as their derived classes, from the inspection scope. In PhpStorm 2018.1, we are providing you with even more control over how you analyze your code: (more…)

We call PhpStorm “an IDE that actually ‘gets’ your code,” meaning that it provides completion, type inference, inspection, documentation pop-ups, and a lot more coding assistance. For all the Standard PHP Library components as well as for common extensions, this functionality is based on PHP stubs. Stubs are normal, syntactically correct PHP files that contain annotated function, method, and class signatures, constant definitions, and so on. The coding assistance quality relies, apart from anything else, on the quality of these signatures and their PHPDoc @annotations provided in the stubs.

How many times you wrote code like this to achieve a simple purpose? Mapping values of an array: foreach ($items as $key => $item) { } Filtering: foreach ($items as $key => $item) {    if (condition($item)) {    } } Or reducing an array to some value: $acc = 0; foreach ($numbers as $number) {    $acc += $number; } The above code samples involve the imperative programming style, which is familiar to everybody. It has a certain flaw: we have to parse the code in our head and go through negligible but required details to understand it. To solve this issue, PHP s

PhpStorm 2017.3 brings you several minor enhancements, allowing for more effective work with unit tests. The new Undefined PHPUnit data provider inspection detects a method that you’ve specified via the @dataProvider annotation but have not declared in unit tests yet. You can quickly create the missing method by applying the suggested Create data provider quick-fix: With the data provider method in place, you can fill it with the test data and run the test as usual: If some of your tests fail, which does happen from time to time, your only option in earlier PhpStorm versions w

What makes PHP great is the community that is building frameworks, libraries and nice tools. And more. This awesome community brought us Composer, a dependency manager for PHP which lets us install and update packages from Packagist.org and makes it easy to package up our own projects and make them available to the world. That awesome community just extended PhpStorm's support for Composer. Next to the UI for managing dependencies and completion for Composer's command line tool that comes with our IDE, Piotr Śliwa's Composer.json plugin for PhpStorm adds completion and inspections for worki

PhpStorm comes with many inspections that help us analyze and improve the quality of our codebase. By using PHP Mess Detector (PHPMD), we can enable many additional code quality checks on our codebase: it can detect possible bugs, suboptimal code, unused parameters and so on. In other words: it tells us if our code is worthy of seeing the daylight. PHPMD also contains several rules that check for complexity of code and will tell us if we should rewrite our code into something that is more maintainable. All these checks are integrated nicely in PhpStorm. Let's have a look at some examples!

Team members may have different backgrounds and code style preferences. In code bases where no formal code style is used, it can become obvious who wrote which code because of different styles being used. Having to work on such code base comes with some drawbacks: developers have to continuously switch their mind around reading code because sometimes brackets are on a new line, sometimes not. Sometimes brackets are required, sometimes not. To ensure a natural flow working with code, a coding standard can be enforced so that the entire code base becomes more uniform to read and work with. In

From time to time we have to mix different programming languages in one file. If there is only one or two occurrences of these small, embedded language islands, using Language Injections is the way to go. But what if we have a lot of them? For example, a JavaScript or CSS file in which we are making use of a PHP variable or function: How do we get mixed syntax highlighting, code completion and inspections? There’s a nice trick to do this: configuring the Template Data Language. This functionality is available in IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, RubyMine and AppCode for various

A lot of PhpStorm users have been asking us to create a series of video tutorials. Today, we're happy to announce the availability of about two hours of video tutorials around PhpStorm which Maarten has been working on for the past few weeks. JetBrains.TV and YouTube playlist are also available. The PhpStorm video tutorials does not cover every feature available nor cover every feature in depth. It is focused around everyday features available in PhpStorm, explained in short bite-size videos of 2-5 minutes. This way you can learn about a new feature every day in just a few minutes! Or if yo

Those of you who have already tried PhpStorm 6 might have noticed a lot of great additions to PHP imports support. In this post we would like to tell you about a long awaited feature: Optimize Imports for PHP. (more…)

There is a number of new PHPDoc inspections available in the latest PhpStorm 2.1 EAP builds which allow to find basic problems in PHP code documenting. These new inspections can be turned on/off in Settings|Inspections|PHP|CodeStyle/PHPDoc. Traditionally each inspection has a quick fix increasing your productivity. (more…)

Pack of fixes in all areas in this build along with couple of new features: PHP completion got new popup layout: added function signatures. Note that you can also open Quick Documentation popup (Ctrl-Q) right from this list. Feedback is appreciated PHP code inspection now checks for implemented methods signature compatibility and dynamic function call variable type Most notable fixes Introduce variable for PHP significantly improved - formatting problems fixed, results of invoking on selection is much more intuitive. Expect better name suggestions and other usability improvements De

We're back to our weekly EAP schedule. After Beta feature freeze you can't expect big features or conceptual changes, however we'll definitely manage to add some neat stuff. Albeit huge pack of bugfixes in all areas this build brings you: Unused local variable inspection for PHP will help you write a cleaner code PHP built-in functions and classes stubs were significantly updated - added missing packages such as intl and other such as SPL, xml and xsl support were fixed Zen coding got its Tab shortcut back (customizable, search for Zen in Settings) Full list is available in issue tracker