PhpStorm 2018.1.2 EAP 181.4668.24

It’s a start of Early Access Program for PhpStorm 2018.1.2, a second minor update for the recently released PhpStorm 2018.1. A fresh build 181.4668.24 is available here, in JetBrains Toolbox App or, if you have installed PhpStorm 2018.1.1 and have “Early Access Program” channel in Settings->System Settings->Updates, 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.

Syntax Highlighting in Quick Definition

Using the Quick Definition popup became more convenient: with added syntax highlighting, you can now read what exactly a function or a class is doing, without losing your current context.

Flexible configuration of imports from the global namespace

In the previous versions of PhpStorm, you could choose to either import everything (functions, classes, constants) from the global namespace or use FQN for functions and constants. We’ve listened to your feedback and realized that more flexibility is sometimes required. In PhpStorm 2018.1.2, you can control auto-import separately for classes, functions, and constants.

For classes, you can choose between “insert FQN” and “prefer import” (PhpStorm will insert import if this doesn’t result in a conflict). For functions and constants, the options are “insert FQN”, “prefer import”, and “prefer fallback” (you can refer to the PHP documentation for its exact meaning).


Notable bug fixes and features worth mentioning:

  • Command Line Tools Console – Cursor Not In Run Box WI-39796
  • Incorrect variable name during phpDoc generation for field in case inferred type in constructor $this WI-40887
  • Provide the ability to disable tooltips in editor without disabling inspections IDEA-114803
  • Subversion File History not working for links with spaces IDEA-185360
  • Typescript readonly type inference from const WEB-32055
  • Add option to omit JsDoc types for TypeScript code WEB-28964

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

Download PhpStorm 2018.1.2 EAP build 181.4668.24 for your platform from the project EAP page 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

This entry was posted in Cool Feature. Bookmark the permalink.
  • CanadianCoder

    I don’t see issue IDEA-187808 fixed in the list. Comeon guys this is a major usability issue

    • Dmitry Tronin

      It’s partly fixed. Our developers are still working on it.

  • Sergey Black

    what about bug with branches? it is horrible, please fix it

  • Sergey Black

    my comment on previos release
    “Each time on git push remote brach is reset to master.
    Plz fix it. Its very annoying.”

  • tarada riduro

    Guys, PHPStorm is really slow after 2018.1 release. It’s impossible to work with it. Highlighting needs every time some seconds to get run the code down. Database tool is more slower as the rest of phpstorm. I’m really angry with it. Also is used ram of up to 2GB is more as acceptable. Nobody needs an editor with a big bundle on tools and possibilities when it’s very very slow and unusable. Most time we are writing code and switching between files and that should not be slow. Regards.

    • Dmitry Tronin

      It would be great to check your logs. Please run Help > Compress Logs & Show in … and send resulting archive over to us via Help > New Support Request.

    • lamka02sk

      Exactly highlighting is sooo slow and with big projects…well there is better no highlighing than every other keyword being maked as warning.

  • tarada riduro

    Look at that ppl. At the moment of taking this screen there were no special big operations. Only javascript debug was on. Not working, just enabled.

    Has anyone similar (performance) issues?

    @dmitry_tronin:disqus and Jetbrains
    Guys, I have not really time to get into your tracker and find out the right place to post an issue, write an understandable description, taking screens or send logs and so on.
    I mean, we pay for your software. Group working is ok at open source projects or free software, where devs don’t earn money for their doing. So, there (in case of open source or free soft) it is ok to take time and help the community to grow and fix existing bugs. But not, if I order my soft for (not few) coins. In this case I wanna get good working tool.

    I hope you understand what I mean, guys. From release to release PHPStorm gets bigger and slower.
    I don’t want to buy a server-machine with 64 gb ram and a hexa-core processor in two years to get phpstorm running :-/

    • Eugene Morozov

      That’s totally understandable, but this behavior may be coming from 3rd party plugins, from WebStorm (from which we acquire JS and HTML and stuff) and from IDEA.
      Without the logs and troubleshooting, there’s no chance we can help you.