Like other EAP builds, this build is free to use but it will expire 30 days after the build date.Įvery PhpStorm release comes with many new inspections to help prevent possible bugs at an early stage while you’re in the editor and the code has not yet been committed. Please report any problems you find to our issue tracker, or by commenting on this post.The fourth build of the PhpStorm 2021.2 Early Access Program comes with a set of new inspections and quick-fixes for PHP, including a whole new group of Refactoring Opportunities inspections. EAP builds are free to use but expire 30 days after the build date.You can install an EAP build side by side with a stable PhpStorm version to try out the latest features.Important! PhpStorm EAP builds are not fully tested and may be unstable.The full list of changes, including bug-fixes and improvements, is available in the release notes. This will ensure that there is enough space to display all the information.Ĭhoose the Compare with Current action from the Git Branches popup menu ( VCS | Branches). With PhpStorm 2020.2, the corresponding actions will show the logs in the editor instead of the Git tool window. Sometimes you want to compare two branches to see which commits do not belong to one another. In the Log tab of the Git tool window, select several commits and choose Squash Commits… from the context menu.īetter presentation of results when comparing branches 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. It will be possible to run PHP CS Fixer and PHPCBF reformatting with a remote interpreter. Reformat quick-fix with remote interpreter 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. It was possible to use PHP_CodeSniffer, PHP CS Fixer, and PHP Mess Detector via Docker, but not Docker Compose. PhpStorm 2020.2 will come with several improvements for code quality tools. You can click it to go straight to the corresponding section of the preferences. Now, if a supported tool is declared in composer.json, there will be a wrench icon in the gutter near it. PhpStorm provides many integrations with third-party tools. Open settings of tools added as dependencies You can quickly jump to package websites right from the composer.json file. Earlier, completion was lost after typing ~, ^, or >=, but now it works as expected. It’s quite common to use range constraints in composer.json. Specify versions constraints with ~, ^, or >= 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. There will be a gutter icon showing the current state of the caching of custom repositories. If you have custom sources specified in the “repositories” section, you will get completion for custom packages. Support for custom Satis/Packagist packages Based on your feedback, there are some improvements in the upcoming 2020.2. PhpStorm 2020.1 introduced support for managing dependencies in the editor right inside the composer.json file. In this blog post, you can read about improvements for Composer, Quality Tools, and VCS. 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. Last week, we launched the Early Access Program for PhpStorm 2020.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |