PhpStorm 2018.2.1 is released

PhpStorm 2018.2.1 build 182.3911.43 is now available! You can download it here or in JetBrains Toolbox App. If you have installed the previous PhpStorm 2018.2 or PhpStorm 2018.2.1 EAP build (182.3911.19), please invoke the Check for updates action to receive the latest update.

This build delivers new features, bug fixes and improvements for PHP and the Web, and takes on the latest improvements in IntelliJ Platform.

New option to disable requirement of PHP bundled extensions in composer.json

New option to disable requirement of bundled PHP extensions in composer.json
PhpStorm 2018.2 introduced a new inspection that helps you to maintain the list of extensions used in a project in composer.json’s require section (e.g., ext-mbstring). If you’ve used a class or function from an unlisted PHP extension, you got the corresponding warning.

Since there are different opinions on whether to report missing bundled extensions or not, PhpStorm now provides you with full control. The behavior is regulated by Settings | Editor | Inspections | PHP | Composer | Extension is missing in composer.json | Require PHP bundled extensions checkbox.

disable_bundled_extensions_requirement

Notable bug fixes and features worth mentioning:

  • Autocompletion became very slow in 2018.2 (FQCN completion) WI-42350
  • Docker-compose PHPUnit with coverage fails WI-42544
  • IAE in EffectPainter2D IDEA-195614
  • No easy way to delete a run configuration IDEA-193775
  • Auto-imports should prefer symlinked file from node_modules to actual file in monorepo projects WEB-30212
  • [TypeScript] RxJS lettable operator – type inference support WEB-32336
  • Web Browsers: support Microsoft Edge browser WEB-19564
  • closure library – code completion for ‘goog.provide’ symbols inside ‘goog.module’ is not working WEB-28405
  • EJS indent options for control block content WEB-15657

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

Download PhpStorm 2018.2.1 build 182.3911.43 for your platform or click “Update” in your JetBrains Toolbox App and please do report any bugs and feature request to our Issue Tracker.

JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Newsletter, Release Announcements. Bookmark the permalink.
  • http://www.xenbyte.com/ Stefan Brauner

    I really like the check of missing extensions in composer.json, but it would be good if I could use a quick fix which adds the extension to my composer.json. And the whole composer thing would be better if I could use a composer in a docker container.

    • https://plus.google.com/+FelipeMartinsKazumi Felipe Martins

      “…, but it would be good if I could use a quick fix which adds the extension to my composer.json.”
      If I get the point, installing extensions is not always way simple and automatic as install a package via composer. Installing extesions involves building/compiling (when cloning from VCS or something like that) and the whole process is tightly OS coupled.

      • http://www.xenbyte.com/ Stefan Brauner

        That’s right. But I just want a quick fix which adds the entry to the composer.json; so just fix the issue which the inspection complains. Just like described in WI-42470 (thanks Pavlo, I voted for it)

    • http://zhukov.zzz.com.ua Pavlo Zhukov
    • Tim Hawkins

      If you load a library in composer, that has a bunch of utility stuff that will support functions that you don’t use, then you don’t want to have to load extensions just because your package manager thinks its needed. Example if you load a database library that has classes to support mysql, postgress, mongo etc, but you only need mysql, you should not need to load those other extensions.

      • sang lin

        Yup.at first i’m kinda oddthe requirement to put like ext-mysqli,ext-json.If just to prevent library such as depreciation ..i’m consider.

  • Tim Hawkins

    One thing of note, its way way way too hard to find posts like this, that discuss the new features and changes to a particular version of an IDE product, would it be possible to add links to toolbox against each product that links to the correct blog post?