未加星标

Completion Changes in PhpStorm

字体大小 | |
[开发(php) 所属分类 开发(php) | 发布者 店小二04 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏

Recent versions ofphpStorm 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 typehinting, PhpDocannotations (and more).


Completion Changes in PhpStorm

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 byusing 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.

Let me know what you think we can do to correct this, or comment on theYouTrack ticket with your opinions. We’re hoping to get this fixed quickly.

Gary and the PhpStorm team

本文开发(php)相关术语:php代码审计工具 php开发工程师 移动开发者大会 移动互联网开发 web开发工程师 软件开发流程 软件开发工程师

主题: PHP
分页:12
转载请注明
本文标题:Completion Changes in PhpStorm
本站链接:http://www.codesec.net/view/481737.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 开发(php) | 评论(0) | 阅读(38)