PhpStorm 2022.1.1 is released
The first minor update for PhpStorm 2022.1 is now available.
You can update to it using the Toolbox App or right from inside the IDE. You can also download PhpStorm 2022.1.1 from the website.
This release mainly brings a bunch of bug fixes and quality-of-life improvements. Let’s take a look!
Improved blade formatting (WI-37087)
The @case and @break directives within a @switch directive weren’t properly formatted by PhpStorm. That’s now fixed.
Default property visibility (WI-50274)
PhpStorm allows you to define the default property visibility in Settings / Preferences | Editor | Code Style | PHP | Properties Default Visibility. However, when automatically generating a property via the constructor, PhpStorm didn’t set the correct visibility. That’s now fixed.
Vite support (WEB-46507)
We now support Vite, the “Next Generation Front End Tooling“!
Rename dynamic fields (WI-65177, WI-65840)
PhpStorm wasn’t able to correctly use rename refactoring combined with dynamic properties. That’s been fixed.
Multiline array formatting (WI-61938, WI-65831)
We’ve made some improvements to how multiline arrays are auto formatted by PhpStorm.
Twig simultaneous delimeter’s editing (WI-65400)
When changing a delimiter in a Twig file, PhpStorm will automatically change its corresponding opening and closing delimiter as well. However, this behavior didn’t work when the expression contained a string (which happens often). This now works properly.
Wrong visibility when changing visibility during inheritance (WI-65245)
PHP allows you to change the visibility of any method or property to a less strict one during inheritance. PhpStorm however didn’t detect these changes in some cases when working with abstract classes.
Fix index error in Magento projects (WI-65276)
PhpStorm 2022.1 had an issue with broken indices in some Magento projects, causing a Null Pointer Exception after indexing those projects. That’s fixed now.
List type in multiline array shapes (WI-65260)
PhpStorm 2022.1 added support for multiline array shapes. However, there were still some edge cases where the list<string> notation wasn’t recognised by PhpStorm as a valid type. The list type, by the way, represents continuous, integer-indexed arrays. In other words: values where the array_is_list function returns true.
Fixes to psalm-import-type (WI-65312)
PhpStorm supports type aliases in doc blocks that you can import and use in other places. However, we didn’t properly detect the use of @psalm-import-type in some cases. That’s now fixed.
False-positive inspections (WI-65988, WI-49455, WI-65879)
Some inspections marked code with a warning when they shouldn’t. Several similar issues have been fixed.
Xdebug “Cannot get property” bugfix (WI-65974)
Our Xdebug integration had some issues not being about to show property information in several cases. Those problems are fixed now.
Array shapes with single quoted keys (WI-65872)
Array shapes weren’t properly detected when using single quoted strings as array keys, that’s fixed now.
False-positive warnings about type mismatch for arrays with multiple element types (WI-57903)
Docblocks that listed arrays with multiple types weren’t interpreted correctly, causing a bunch of warnings about type mismatches between docblocks and PHP types. These problems are now fixed.
FTP sync errors (WI-66158, WI-65678)
PhpStorm 2022.1 had some issues when trying to use FTP to sync code between a server and your local development environment. Those issues are now fixed.
Rsync errors on Windows (WI-66118)
PhpStorm 2022.1 introduced some issues with Rsync on Windows where some files would end up using the wrong paths or where an error would occur when syncing. These problems are now fixed.
You can read the release notes in full here.
That’s all for today. Thanks for keeping up with the changes! We hope they improve your PhpStorm experience.
- Download PhpStorm.
- Tweet @ us!
- Report bugs to our issue tracker.
Your JetBrains PhpStorm team
The Drive to Develop
Subscribe to PhpStorm Blog updates
