<\/i>Download PhpStorm 2019.3 EAP<\/a><\/p>\n If you\u2019re not yet familiar with our Early Access Program, here are the basics you should know:<\/p>\n PHPDoc blocks in PHP are an integral part of development. They can even affect the execution if you are using advanced annotations and AOP techniques. Let us know how you like the changes and what we should improve!<\/p>\n The conditional If you have an assignment inside an If you have nested You can merge Or do the opposite and split Short tags are likely to remain a part of PHP at least for the next few years, as the last RFC vote<\/a> did not pass.<\/p>\n But PhpStorm will help you a bit with deprecating short tags, by automatically inserting Another small timesaver in the upcoming 2019.3. When you are adding an item into an array, and you type a key and then want to type While coding, we sometimes spend more time reading than writing, so coloring and highlighting really matters. In 2019.3, you will be able to choose the font and colors for occurrences of What else would you like to have improved in highlighting? Let us know!<\/p>\n Sometimes, when you are looking through a version history log, it\u2019s easier to comprehend the information if the time is displayed in a relative format. Or, if you are from the US, you are most likely used to mm\/dd\/yyyy.<\/p>\n In PhpStorm 2019.3, it is possible to configure the date format for VCS Annotate and VCS Log actions.<\/p>\n In fact, we’ve added the API for date\/time customization in the IntelliJ Platform, and we will add more UI areas where date and time formats are important. Feel free to create feature requests for them.<\/p>\n Some time ago we introduced initial support for GitHub Pull Requests, to let you view the list of all Pull Requests in the project and browse through them to see the changes and their current status. While it was great to have this ability in the IDE, there were some known limitations, for example, being unable to view reviewers\u2019 comments.<\/p>\n The upcoming PhpStorm 2019.3 will add this missing piece to the picture. It will display a timeline with all the relevant information about a pull request such as comments, reviews, and updates made to pull requests \u2013 basically, all the information you may need to make a decision whether or not to merge this pull request. For the full list of changes in this build, including both bug-fixes and improvements, consult the release notes<\/a><\/strong>.<\/p>\n\n
PHPDoc<\/h2>\n
\nTraditionally in PhpStorm, you had resolving for FQNs and links in PHPDoc, but the whole block was displayed in one color and styled just like regular comments.
\nNow, starting with PhpStorm 2019.3, doc blocks will get full highlighting for all the types, variables, params, methods, and properties. If you have HTML in your comments, it will also be highlighted as such.<\/p>\n![\"phpdoc-light-theme\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-phpdoc-light-theme.png\")
<\/p>\nQuick-fixes for conditions<\/h2>\n
if-else<\/code> statement is probably the most used construct in the language. So in PhpStorm 2019.3, we\u2019ve added a few quick & neat actions to manipulate conditions.<\/p>\nif<\/code> statement, PhpStorm will suggest extracting it to a variable with Alt+Enter<\/em>:<\/p>\n![\"if-assignment-extract\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-if-assignment-extract.png\")
<\/p>\nif<\/code> conditions, it is now possible to quickly merge them into one with Alt+Enter<\/em>:<\/p>\n![\"if-merge-conditions\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-if-merge-conditions.png\")
<\/p>\nelse<\/code> followed by if<\/code> into a single elseif<\/code>:<\/p>\n![\"else-if-merge\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-else-if-merge.png\")
<\/p>\nelseif<\/code> into else<\/code> and if<\/code>:<\/p>\n![\"elseif-split\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-elseif-split.png\")
<\/p>\nOther Improvements<\/h2>\n
Auto-insert <?php when just <? is typed in<\/h4>\n
<?php<\/code> as soon as you type <?<\/code>:<\/p>\n![\"php-no-short-tag\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-php-no-short-tag.gif\")
<\/p>\nAutomatically complete ‘=’ to ‘=>’ after array key<\/h4>\n
=><\/code> to specify a value, just press =<\/code> and PhpStorm will auto-insert =><\/code>:<\/p>\n![\"array-quick-typing\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-array-quick-typing.gif\")
<\/p>\nFonts & colors for $this variable<\/h4>\n
$this<\/code>:<\/p>\n![\"this-color-and-fonts\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-this-color-and-fonts.png\")
<\/p>\nVCS<\/h2>\n
Date format customization<\/h3>\n
![\"vcs-date-formats\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-vcs-date-formats.png\")
<\/p>\nTimeline for GitHub Pull Requests<\/h3>\n
\nSimply double-click a pull request, and the IDE will display the comments in the editor tab.<\/p>\n![\"github-timeline\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2019\/09\/phpstorm-github-timeline.png\")
<\/p>\n