Features

Why is static code analysis important? How can you benefit from adding another step in the project lifecycle? Find the answers to these questions and others in our blog post.

Qodana specializes in build quality management, delivering the static analysis smarts of IntelliJ Platform to project-level checks. In May, we extended the platform with a second linter,  Clone Finder, which detects code duplicates. Today, we are happy to announce the EAP for License Audit to detect incompatible third-party licenses on which your code relies, making the compliance verification process easier for your project and company. Qodana License Audit is still very much in the early stages, but making it available earlier helps us to catch problems earlier. This makes prepar

In December 2020, we announced the EAP for Qodana, which is rapidly evolving into a comprehensive platform that allows companies to perform multi-level evaluations of the quality of code they own, contract, or purchase. Qodana helps you detect bugs without relying on an IDE, either on a local machine or a build server, and it is designed to be seamlessly integrated into CI/CD pipelines. In addition to delivering static analysis for automated project-level evaluations, the Qodana team is developing additional audit features. One of them is Clone Finder, which looks for duplicates in software r

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…)

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