<\/i>Download PhpStorm 2020.2 EAP<\/a><\/p>\n <\/p>\n PhpStorm 2020.1 introduced support for managing dependencies in the editor<\/a> right inside the composer.json file. Based on your feedback, there are some improvements in the upcoming 2020.2.<\/p>\n Support for custom Satis\/Packagist packages<\/strong> There will be a gutter icon showing the current state of the caching of custom repositories. <\/p>\n Completion for multiple versions<\/strong> Specify versions constraints with ~, ^, or >=<\/strong> Link to homepage\/sources<\/strong> Open settings of tools added as dependencies<\/strong> PhpStorm 2020.2 will come with several improvements for code quality tools.<\/p>\n Docker Compose Support<\/strong> Exclude Patterns for PHP_CodeSniffer<\/strong> Reformat quick-fix with remote interpreter<\/strong> If you have a number of redundant commits, say some work-in-progress ones, you can now combine them into a single one to clean up the history before pushing.<\/p>\n In the Log<\/em> tab of the Git<\/em> tool window, select several commits and choose Squash Commits\u2026<\/em> from the context menu.<\/p>\n Sometimes you want to compare two branches to see which commits do not belong to one another.<\/p>\n With PhpStorm 2020.2, the corresponding actions will show the logs in the editor instead of the Git<\/em> tool window. This will ensure that there is enough space to display all the information.<\/p>\n Choose the Compare with Current<\/em> action from the Git Branches<\/em> popup menu (VCS | Branches<\/em>).<\/p>\n The full list of changes, including bug-fixes and improvements, is available in the release notes<\/strong><\/a>.<\/p>\n Please report any problems you find to our issue tracker<\/a>, or by commenting on this post. Your feedback is much appreciated, and the most active EAPers will get special limited-edition gifts<\/a> from us!<\/p>\n Your JetBrains PhpStorm team<\/em>Composer<\/h2>\n
\nIf you have custom sources specified in the \u201crepositories\u201d<\/code> section, you will get completion for custom packages.<\/p>\n![\"composer_custom_repos\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/06\/phpstorm-composer_custom_repos.png\")
<\/p>\n
\nWhen a package has multiple versions separated with a comma or pipes (||<\/code>), PhpStorm will now handle it properly and provide completion with all available versions for this package.<\/p>\n![\"composer_range-versions.\u0441mproj\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/06\/phpstorm-composer_range-versions.\u0441mproj.png\")
<\/p>\n
\nIt\u2019s quite common to use range constraints in composer.json. Earlier, completion was lost after typing ~<\/code>, ^<\/code>, or >=<\/code>, but now it works as expected.<\/p>\n
\nYou can quickly jump to package websites right from the composer.json file.<\/p>\n![\"composer_pages_links\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/06\/phpstorm-composer_pages_links.png\")
<\/p>\n
\nPhpStorm provides many integrations with third-party tools. Now, if a supported tool is declared in composer.json, there will be a wrench icon in the gutter near it. You can click it to go straight to the corresponding section of the preferences.<\/p>\n![\"composer_open_settings\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/06\/phpstorm-composer_open_settings.png\")
<\/p>\nQuality Tools<\/h2>\n
\nIt was possible to use PHP_CodeSniffer, PHP CS Fixer, and PHP Mess Detector via Docker, but not Docker Compose. This has been resolved.<\/p>\n![\"quality_tools_docker-compose\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/06\/phpstorm-quality_tools_docker-compose.png\")
<\/p>\n
\nIf your custom ruleset.xml has an "exclude-pattern" section, PhpStorm will now take it into account and not analyze files under the specified path.<\/p>\n
\nIt will be possible to run PHP CS Fixer and PHPCBF reformatting with a remote interpreter.<\/p>\nVCS<\/h2>\n
Squashing local commits from the log<\/h3>\n
![\"vcs_squash\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/06\/phpstorm-vcs_squash.png\")
<\/p>\nBetter presentation of results when comparing branches<\/h3>\n
![\"vcs_compare_branches\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/06\/phpstorm-vcs_compare_branches.png\")
<\/p>\n
\n\n
\nThe Drive to Develop<\/em><\/p>\n","protected":false},"author":869,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","categories":[826],"tags":[192,2583,285,2615,284],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/phpstorm\/21764"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/phpstorm"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/types\/phpstorm"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/users\/869"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/comments?post=21764"}],"version-history":[{"count":0,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/phpstorm\/21764\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/media?parent=21764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/categories?post=21764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/tags?post=21764"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/pt-br\/wp-json\/wp\/v2\/cross-post-tag?post=21764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}