The Early Access Program for PhpStorm 2020.2 is in full swing and today we’ve got the third build of the 2020.2 EAP for you. In this blog post, you can read about improvements for Git installed in WSL2 and Search Everywhere. Download PhpStorm 2020.2 EAP (more…)

We’ve just rolled out a preview for the third minor update for PhpStorm 2019.3. Please give the PhpStorm 2019.3.3 Preview build 193.6494.5 a try and share your feedback with us. (more…)

Check out our fresh video with a few nice tips and tricks on how to update your codebase to PHP 7.4. It combines materials from the PhpStorm 2019.2 and PhpStorm 2019.3 releases, with a few cool bonuses to boot. Nikita drew our attention to the fact that setters are slower than assigning properties directly. We had to make a microbenchmark. You can't take Nikita's word for it, can you?! So in the video, don’t miss the guide on creating a custom inspection and quick-fix to convert setters to property assignments. Your JetBrains PhpStorm Team The Drive to Develop

PhpStorm 2019.3.1 build 193.5662.63 is available now. It brings with it important bugfixes and a couple of small but heavily requested usability improvements. Customizable auto-insertion of short tags PhpStorm 2019.3 introduced the ability to automatically insert <?php as soon as you type <?, which can help you deprecate short tags: But because short tags are still a part of PHP, this turned out to be a bit excessive. That is why in this version, we’ve brought several enhancements to the feature. First, you can now opt out completely. In the PhpStorm preferences, go to Edit

When developing a web service, you would usually test it by sending all kinds of HTTP requests to it and examining what’s returned. In PhpStorm, you can do this directly in the code editor. In this post, we’ll use the github.com/JetBrains/phpstorm-http-client-tutorial example project to demonstrate. You can clone it and navigate through its commit history to get to the corresponding phase of this overview. For each phase, run composer update to install and update what’s required, and then composer start to start the PHP web server. (more…)

We've just released PhpStorm 2019.2, and today we are ready to give you a preview of the second bugfix update. Please try PhpStorm 2019.2.2 Preview build 192.6603.14 and share your feedback with us. Improved Type Inference We've made a lot of changes in the PHP type inference system, which affect the handling of $this/self/static return types. The following long-standing issues, as well as many others, are now fixed: WI-28728 +18 Fixed: No code completion in foreach loop if array of object is generating from static method with static array type hint WI-18067 +18 Fixed: Late Static Bind

We’re close to releasing PhpStorm 2019.2.1, the first minor update for PhpStorm 2019.2, and today we are ready to give you a Release Candidate. Please try PhpStorm 2019.2.1 RC build 192.6262.47 and share your feedback with us. This RC build brings with it important bugfixes, performance, and usability improvements, as well as regression fixes. Here are some notable updates: Fixed: Can't write caret (^) and tilde (~) on Czech keyboard JBR-1743 Fixed: Can't insert backticks in the editor JBR-1744 Fixed: Drupal hook completion in other PHP files (profile and install files) WI-46972 Fixe

The third build of the PhpStorm 2019.2 EAP (192.4787.17) is now available! With this build you can try the following new features: PHPT support, new intentions in String Juggling Toolbox, Method Breakpoints via gutter, shell scripts support, automatic suggestions of related files while you commit to a VCS. As usual, all the updates from Web, DB, and the IntelliJ Platform are included! Download PhpStorm 2019.2 EAP from the EAP page or via the JetBrains Toolbox App. Or, if you have the previous PhpStorm 2019.2 EAP build (192.4488.6) installed, you should soon get a notification in your ID

In PhpStorm 2019.1, we’ve implemented debugging of Twig and Blade templates. The problem was that template files are not the files your application runs. They are first compiled into regular PHP and saved to a cache directory, and then the application runs those compiled files. So before PhpStorm 2019.1, your only option was to identify the compiled file, something like b84f5d6c0f0d85bb9187843.php, locate the line you want to place a breakpoint on, and then debug this file instead. Luckily, things have changed, and you can now debug your template files directly – there’s no difference

We’re close to releasing PhpStorm 2019.1.2, the second minor update for PhpStorm 2019.1, and today we have another preview build for you. Please give PhpStorm 2019.1.2 Preview build 191.7141.35 a try and share your feedback with us. This update brings support for Composer via Docker and has bug fixes and improvements for PHP, support for the Web, and enhancements from IntelliJ Platform. Support Docker for Composer execution PhpStorm has support for PHP interpreters via Docker and Docker-compose, but it still missed Composer integration with Docker. You needed a local PHP setup in order to

In 2019.1 release, we’ve reworked the inspections and intention actions related to importing namespaces and using FQN. We’ve also added some PHP-specific intentions to the Code Cleanup tool, which will help you automatically run safe transformations on the whole project or a part of it. (more…)

Every week brings you a fresh update to PhpStorm, and this one is no exception. Meet the preview for PhpStorm 2019.1.2! Try PhpStorm 2019.1.2 Preview build 191.7141.5 and share your feedback with us. This Preview build brings with it important bug-fixes, performance and usability improvements, and regression fixes. Notable updates: Blade debug: Support new format of Blade debug info (WI-46191 +1) Laravel 5.8.11 has modified the Blade debug info format, so you'll need to update PhpStorm to the current build to bring debugging Blade templates experience back. Thanks a lot to the Lara