![]() You have long asked us to support the parallel running of tests with ParaTest. We’ll continue to improve PhpStorm’s support for popular templating engines.įor Blade, we’d like to add completion for closing directives, highlighting of paired directives, and support for the readonly directive.įor Twig, we’ll add resolve for functions in templates.Īnd for both Blade and Twig, we’re going to implement better tracking of unused functions and reduce false positives. Wildcards in PHPDoc for constant enumerations.Parsing of Palm template declaration with restrictions.The next release should be no exception as we plan to support the following features: Since the initial announcement, we’ve continued to improve PhpStorm’s support for Psalm and PHPStan annotations. We’ll be happy to not only help address your issue, but also to use this feedback to make the PhpStorm debugging experience better for all users! If you have experienced any difficulties setting up the debugger in PhpStorm, please tweet us post a comment below, or submit a ticket from the IDE by selecting Help | Submit a Bug Report. We won’t be able to solve all the problems with setting up the debugger before 2022.3 comes out, but we’d like to take the first steps and make it easier to start debugging in PhpStorm right away. But setting it up can sometimes be tricky. Having a debugger on hand during development can save you hours of time. We plan to add support for it in the next PhpStorm update, too. Xdebug 3.2 will have an extra “return from function” debugging step, in which you can inspect the return value. When you hit a breakpoint while debugging a test, it will be possible to play around with the code right away in the console. Interactive debug console while debugging PHPUnit tests ![]() This is where global conditional breakpoints can be useful. For instance, imagine you want to see what code in a framework changes $_SЕRVER, but you have no idea where to set a breakpoint. ![]() Sometimes you may want to set a breakpoint that is not tied to any file or line. There are several major areas that we want to improve in PhpStorm’s debugging experience. We want to update the existing Move static member refactoring that would allow quickly converting a class with constants to a corresponding enum with cases. Since PHP 8.1, this problem is more easily solved by using enums. Extract constant classes to enumīefore PHP 8.1, it was common to use classes as containers for a set of constants. We plan to improve and make the refactoring reliable with complex configurations. However, right now this only works if autoloading is properly configured. Now we’d like to bring the same experience for PHP.Įarlier this year, we added the ability to drag classes and folders in the project tree. We’d like to add a way to render PHPDoc blocks right in the editor in an easier-to-read format. We want to give you the ability to preview the results of a quick-fix or intention before you actually go apply it. Some code problems in PhpStorm can be fixed automatically by pressing Alt+Enter. We’d like to make this possible for PHP code, as well. These can be, for example, the number of times a method was used, the name of the Git user who has changed the code section most often, i.e. PHP 8.2 will come with a few deprecations, so PhpStorm 2022.3 will include convenient inspections and quick-fixes to make it easier for you to upgrade.Ĭode Vision is a popular feature available in IntelliJ IDEA, Rider, and the other JetBrains products that gives you interactive hints right in your code. The new version of PHP is expected for public release at the end of November, and PhpStorm will provide full support for it from day one. Our top priority will be improving the IDE’s stability and performance on many levels, including reducing UI freezes, speeding up highlighting in editor, and so on. What’s coming in PhpStorm 2022.3 Quality and performance Let us know what you think so we can take your feedback into account in making PhpStorm even better. Please note the plan is subject to change, and we cannot guarantee that all of the items below will make it into version 2022.3. So this time, we want to share with you our public plan for the next release. We always strive to be more transparent and collect feedback from you, our users, as early as possible. From the beginning, our task tracker has been open, allowing anyone to send us bug reports or suggest new features. PhpStorm has been around for more than 10 years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |