Completion Changes in PhpStorm
Recent versions of PhpStorm have changed the way code completion works in PhpStorm, and it’s caused some confusion. Let’s take a look at how completion works in PhpStorm 2016.2.
Completion was updated with the 2016.2 release to try and make the most relevant objects or parameters float to the top of the completion list, and removing some methods or variables. This should save us keystrokes and time finding what we are looking for, but it appears that this has had some unintended consequences.
When you invoke completion (using CTRL+Space by default) and PhpStorm can identify the type of the item you need to complete, it will now float elements of that implied type to the top of the completion list. PhpStorm can imply the type in various ways, from the variable assignment, PHP 7’s type hinting, PhpDoc annotations (and more).
Here you can see that because the `acceptsBoolean` function only takes a `bool` (as defined by the PHP 7 scalar type hint), the `$isChipped` variable gets floated to the top as it’s the only boolean we’ve defined in scope.
Also useful is the new way that we can invoke a filtered completion list by using Shift+CTRL+Space; this will remove any items that aren’t of the inferred type from the list completely. This is all good and makes finding the right thing to complete with quicker and easier.
The next completion change was to remove static methods from the completion list when completion is invoked in the context of `$this->`. This change happened as a result of a ticket opened by a user a few years ago. Calling static methods using `$this->` is an entirely valid use case but is not that widely used in PHP. While this seemed like a good idea at the time, it’s had the unintended consequences of making writing assertions in PHPUnit a little more painful.
PHPUnit’s assertions are written as static methods, but are usually called in the context of `$this` to make tests clean and readable. This latest change has therefore meant that when writing PHPUnit tests, you don’t get the `assert*` methods in the code completion list. Obviously, this is a Bad Thing™. You can get the full list of methods by invoking code completion for the second time, but this extra keypress has got some people (rightly) annoyed.
It seems we may have made a mistake here, albeit with the best intentions, but we’re working on fixing it. Current thinking is to show the complete completion list if completion is invoked in the context of a PHPUnit test, but we haven’t come to a firm decision yet.
– Gary and the PhpStorm team
Subscribe to Blog updates
Thanks, we've got you!
Qodana Clone Finder: Early Access Program
In December 2020, we announced the EAP for Qodana, which is rapidly evolving into a comprehensive platform that allows companies to perform multi-level evaluations of the quality of code they own, contract, or purchase. Qodana helps you detect bugs without relying on an IDE, either on a local machi…
PhpStorm 2020.2 EAP #3
The Early Access Program for PhpStorm 2020.2 is in full swing and today we’ve got the third build of the 2020.2 EAP for you. In this blog post, you can read about improvements for Git installed in WSL2 and Search Everywhere. Download PhpStorm 2020.2 EAP (more…)…
PhpStorm 2019.3.3 Preview
We’ve just rolled out a preview for the third minor update for PhpStorm 2019.3. Please give the PhpStorm 2019.3.3 Preview build 193.6494.5 a try and share your feedback with us. (more…)…
How to Upgrade to PHP 7.4 with PhpStorm
Check out our fresh video with a few nice tips and tricks on how to update your codebase to PHP 7.4. It combines materials from the PhpStorm 2019.2 and PhpStorm 2019.3 releases, with a few cool bonuses to boot. Nikita drew our attention to the fact that setters are slower than assigning prop…