PhpStorm 2016.3 EAP 163.6512

The new PhpStorm 2016.3 EAP build (163.6512) is now available! You can download it here or, if you have installed the previous PhpStorm 2016.3 EAP build (163.6110), 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.

Initial support of CodeIgniter Framework

Good news for the CodeIgniter users! We’ve added an initial support of CodeIgniter Framework. Now after you enable the CodeIgniter support you will get the support of the code style, also CodeIgniter inspection profile will be set up automatically.

codeinte

New naming inspection for constants

In previous build we’ve added new naming convention inspections. Now new naming convention inspections are also available for constants.  These inspections will highlight those constants that don’t follow naming convention in current project.

constant

Improvements in PHPSpec support

We are continue working on PHPSpec support in PhpStorm. This build brings support of spec_prefix and beConstructedThrough method in addition to the previously introduced features.

phpspec11

Apart new features, this build brings many bugfixes, the most remarkable of them:

  • Fix of WI-33542: SSH Deployment server can’t be used for Remote Tools
  • Fix of WI-31754: Regression with Recursive resolve of constant values inside include expressions

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

Learn more about other new features in PhpStorm 2016.3:

  • PhpStorm 2016.3 EAP, 163.3512: Ability to open several PhpStorm projects in one frame, support of Docker in remote interpreters, completion of overridden methods and fields without function and var keyword, project wide PHP 7 strict types, and more
  • PhpStorm 2016.3 EAP, 163.3983: Code Style Settings for PHP 7 return types
  • PhpStorm 2016.3 EAP, 163.4396: New extension point that allows to provide PHP files into projects, quick fix for case-insensitive inspection, composer doesn’t add vendor subfolders to External Libraries, improved VCS Log
  • PhpStorm 2016.3 EAP, 163.4830: Semantic highlighting for variables and parameters, new setting to select variable name without ‘$’ on double click, and more.
  • PhpStorm 2016.3 EAP, 163.5644: Initial PHPSpec support, faster Search in Git Log, managing Git remotes and other improvements.
  • PhpStorm 2016.3 EAP, 163.6110: New naming convention inspections, PHPSpec Run Configurations.

Download PhpStorm 2016.3 EAP build 163.6512 for your platform from the project EAP page and please do report any bugs and feature request to our Issue Tracker.

Your JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Early Access Program and tagged . Bookmark the permalink.
  • Stefan Cuculeac

    How about better support for Laravel?
    great job!

    • Maxim Kolmakov

      There is a great plugin https://plugins.jetbrains.com/plugin/7532?pr=idea that supports Laravel. Do you miss anything in particular?

      • Stefan Cuculeac

        Yes i have allready that plugin, which works great but there are things to could be improved like click on Route uses Controller for instance. http://screencast.com/t/oF4hazblaN

      • Evgeniy Nikonorov

        Yep. Code inside {{ }} blade templates directives.
        It’s regular php code but it’s not recognized by Ide in ‘Find usages…’ @var type comments, autocompletition etc. It’s recognized as simple text.
        As u like to say: “it’s not trivial to implement”.
        Full support of codeIgniter is trivial ofc, make Ide to parse text inside {{ }} structures is hard job.
        Well done!
        Thank You.

      • Alex

        There is no code completion in cases:
        1. This one is most annoying:
        <?php
        /**
        * @var array $array
        * @var SomeObject $obj
        */
        {{ $array[0] }} {{ $obj->field }} {{ $obj->method() }}
        ?>
        2. Less annoying because it actually soyuld not be used in template but actually happens rarely

        {{ $array[0] }}

        For both cases there is no autocompletion for var names, object fields and methods.
        The issue here were ignored for 2 years soon: https://youtrack.jetbrains.com/issue/WI-26501

    • BJ

      laravel le stinks.

  • http://gilbarbara.github.io/ Gil Barbara

    No stylelint inline checks yet? I’ve tried Webstorm EAP and it is working for the last 2 or 3 versions.

    • Maxim Kolmakov

      The stylelint inspection is included in this EAP. Please check “Settings->Inspections->CSS->Code quality tools->Stylelint”.

      • http://gilbarbara.github.io/ Gil Barbara

        Yeah, it’s working that way, but in Webstorm the inspector runs directly in the editor.

        • Maxim Kolmakov

          The behaviour should be the same in PhpStorm. If you enable the checkbox inspection will be run in editor as well.

          • http://gilbarbara.github.io/ Gil Barbara

            Ahh!
            Stylelint won’t display errors in the editor while the scss-lint plugin is loaded..

  • darthyoda6

    Thanks for adding the CodeIgniter framework.

    Where do I go to turn it on or change any settings for it? Or is it in the plugins page and checked by default?

    • Maxim Kolmakov

      At the moment you can set CodeIgniter code style in Settings->Code Style->PHP->Set From…
      We’re still working on other features at the moment.

  • Roger Goll

    How do I enable codeigniter support? You show that support is possible in this version but do not say how …