PhpStorm 2020.2 EAP #2
Last week, we launched the Early Access Program for PhpStorm 2020.2. For the next two months, we are going to be releasing updates every week, and today we’ve got the second build of the 2020.2 EAP for you.
In this blog post, you can read about improvements for Composer, Quality Tools, and VCS.
PhpStorm 2020.1 introduced support for managing dependencies in the editor right inside the composer.json file. Based on your feedback, there are some improvements in the upcoming 2020.2.
Support for custom Satis/Packagist packages
If you have custom sources specified in the
“repositories” section, you will get completion for custom packages.
There will be a gutter icon showing the current state of the caching of custom repositories.
Completion for multiple versions
When a package has multiple versions separated with a comma or pipes (
||), PhpStorm will now handle it properly and provide completion with all available versions for this package.
Specify versions constraints with ~, ^, or >=
It’s quite common to use range constraints in composer.json. Earlier, completion was lost after typing
>=, but now it works as expected.
Link to homepage/sources
You can quickly jump to package websites right from the composer.json file.
Open settings of tools added as dependencies
PhpStorm 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.
PhpStorm 2020.2 will come with several improvements for code quality tools.
Docker Compose Support
It was possible to use PHP_CodeSniffer, PHP CS Fixer, and PHP Mess Detector via Docker, but not Docker Compose. This has been resolved.
Exclude Patterns for PHP_CodeSniffer
If your custom ruleset.xml has an "exclude-pattern" section, PhpStorm will now take it into account and not analyze files under the specified path.
Reformat quick-fix with remote interpreter
It will be possible to run PHP CS Fixer and PHPCBF reformatting with a remote interpreter.
Squashing local commits from the log
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.
In the Log tab of the Git tool window, select several commits and choose Squash Commits… from the context menu.
Better presentation of results when comparing branches
Sometimes you want to compare two branches to see which commits do not belong to one another.
With PhpStorm 2020.2, the corresponding actions will show the logs in the editor instead of the Git tool window. This will ensure that there is enough space to display all the information.
Choose the Compare with Current action from the Git Branches popup menu (VCS | Branches).
The full list of changes, 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.
Your JetBrains PhpStorm team
The Drive to Develop