PhpStorm 2020.1 EAP #4

Posted on by Roman Pronskiy

The Early Access Program continues, and the fourth build for PhpStorm 2020.1 is now available!
This blog post is dedicated to updates in advanced metadata support.

If you prefer to watch the updates on YouTube, you can subscribe to the JetBrains channel and follow our What’s Coming in PhpStorm 2020.1 SeriesEpisode 2 is already online!

Download PhpStorm 2020.1 EAP

Metadata

As you may know, there is a way to extend PhpStorm’s “code awareness” by providing additional information in a special file .phpstorm.meta.php. For example, this is exactly how container access works in barryvdh/laravel-ide-helper or additional features in Symfony plugin thanks to King2500/symfony-phpstorm-meta.

To learn more about metadata capabilities, you can check the PhpStorm advanced metadata help page or New .phpstorm.meta.php features blog post.

In the upcoming PhpStorm 2020.1, this meta feature gets a few upgrades.

Parameter index in override, map, and type

Previously, with override(), map(), and type() directives, it was possible to adjust behavior only of the first parameter of the functions. In PhpStorm 2020.1 this finally will be fixed, and it will be possible to specify the index of the parameter explicitly:

metadata_argument_index_metafile

metadata_argument_index

Support for property access via __get

If you had to receive some objects via the __get() magic method, then you would likely lose type information. To make it available, you then had to add either a @var or a @property tag. The latter is not applicable in case you didn’t know the type beforehand.

For example, let’s say you had a ServiceManager and in its foo property you wanted to expect to have FooService. In 2019.3, this was not possible.

metadata_getter_2019

Now it will be possible to provide such information via metadata.

metadata_getter_metafile
metadata_getter_2020

Completion for keys in ArrayAccess objects

If you’d like to use some object as an array container for other objects and still have code completion, this worked as expected with metadata assistance. However, there was no completion for available keys. Now this will be added in 2020.1.

metada_arrayaccess_metafile
metada_arrayaccess

Custom exit points

PhpStorm considers the functions die() and exit() or the ones throwing an exception as terminating calls. But in applications, there may be some other custom functions that have to be considered as “exit points”, for example, if it’s a debugging function like dd() or error function like trigger_error with E_USER_ERROR argument.

metadata_exitpoint_2019

In PhpStorm 2020.1, it will be possible to mark any function as a custom exit point. This will effectively make a control flow engine take all these function calls into account.

metadata_exitpoint_metafile
metadata_exitpoint_2020

Gutter icon for functions with meta overrides

And last but not least, in the editor you will now see if the behavior was modified by .phpstorm.meta.php file with override(), exitPoint(), or expectArguments() directives. And since there can be any number of such metafiles in the project, by clicking the icon, you will open the one that is used in this specific place.

metadata_guttericons

You can hide these icons under Preferences/Settings | Editor | General | Gutter Icons.


The full list of changes in this build, including bug-fixes and improvements, is available in the release notes.

  • Important! PhpStorm EAP builds are not fully tested and may be unstable.
  • You can install an EAP build side by side with a stable PhpStorm version to try out the latest features.
  • EAP builds are free to use but expire 30 days after the build date.

Please report any problems you find to our issue tracker, or by commenting on this post. Your feedback is much appreciated, and the most active EAPers will get special limited-edition gifts from us!

Your JetBrains PhpStorm team
The Drive to Develop

Subscribe

Subscribe for updates