PhpStorm 2018.3 EAP 183.2407.8

Posted on by Roman Pronskiy

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

Download PhpStorm 2018.3 EAP

This build delivers basic DQL support, autodetecting non-PSR coding standards for PHP_CodeSniffer, improved completion performance, a bunch of bug fixes and improvements for PHP and the Web, and includes the latest enhancements of IntelliJ Platform.

Doctrine Query Language Support

While you can use raw SQL with Doctrine, the preferred way to make queries is by using DQL. DQL as a query language for your object model. It means that in your queries you’ll be using PHP classes’ and fields’ names to fetch or update data. Learn more about DQL in the documentation.

Before PhpStorm 2018.2.3, DQL queries were inspected as SQL and therefore highlighted as containing errors. In PhpStorm 2018.2.3, injections of SQL inside text literals were automatically disabled for strings with DQL identifiers.

In PhpStorm 2018.3, we introduce basic DQL support: your DQL queries will now be properly highlighted.


In the upcoming builds, we plan to deliver automatic injecting as well as autocompletion for entities and fields. Please let us know what else would be great to add to make DQL support complete.

Autodetect non-PSR coding standards for PHP_CodeSniffer

When developing with one of the major Frameworks or CMSs, you may add the corresponding coding standards package to you composer.json to ensure the quality and style compliance.

In PhpStorm 2018.3, the following standards will be detected automatically:

If you have both PHP_CodeSniffer and one of the Standards added to you composer.json dependencies, then the corresponding inspection will be turned on.

Other PHP features worth noting

  • It’s now possible to use Macros in arguments for PHP Script run-configuration (WI-43456 ).
  • PHP completion performance improved.

Other platform features worth noting

  • You may set per-project custom plugin repositories (IDEA-130730)
  • Added support for drag-and-drop files in welcome screen (IDEA-57019)
  • When doing Git submodule commit, parent repository now re-requests Git status to show updates to the submodule folder (IDEA-100075)
  • It’s possible to sort CSS properties by name inside a declaration (WEB-22)

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

Future plans

Use the board to view the up-to-date list of the features planned for 2018.3 release, as well as discovered bugs. The list only reflects our current plan and is not final. It may be revised during development since new issues may appear and existing may be re-planned to appear in later versions. Please share your opinions on what is important to you and what would you like to see in the new version!

Download PhpStorm 2018.3 EAP build 183.2407.8 for your platform 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.

11 Responses to PhpStorm 2018.3 EAP 183.2407.8

  1. Navarr Barnier says:

    September 12, 2018

    For Magento, addition of would also be great

    • Maxim Kolmakov says:

      September 12, 2018

      Unfortunately, addition of these sniffs are not so straightforward as others since we will have to determine the version of Magento. Besides, the package is not in official packagist repository so it’s hard to us to evaluate how popular the package really is.

  2. Константин says:

    September 12, 2018

    Please fix bug with search

    • Eugene Morozov says:

      September 13, 2018

      From what I can see, the platforms guys are having a hard time reproducing the issue.
      I’ll leave a comment with a link to this thread there. Sorry for any inconvenience caused.

  3. Stefan Brauner says:

    September 12, 2018

    What about the Zend Coding Standard? It’s currently used by every Zend Framework and Zend Expressive module and maybe also by the most projects build with those framework. The current version is two years old, but in the Pull requests I saw that they are working on a new version in the last days.

    Would be cool if it’s possible to use some of those rules for the PHP Code Style (for code formatting).

    • Maxim Kolmakov says:

      September 13, 2018

      Thank you for the suggestions! We will add Zend Coding Standard in the next EAP.
      Regarding the application of rules from PHPCS to PhpStorm Code Style, that is very hard to do and will require a lot of work. We may implement though so please vote.

  4. jtraulle says:

    September 13, 2018

    Why not adding CakePHP coding standard ?

    • Maxim Kolmakov says:

      September 13, 2018

      Thank you for the suggestions! We will add this one in the next EAP.

      • jtraulle says:

        September 14, 2018

        Great, thanks 🙂

  5. Luis Lobo Borobia says:

    September 13, 2018

    Hi, What about Yii2 Coding Standard?


Subscribe for updates