False-positive warnings about type mismatch for arrays with multiple element types ( WI-57903)ĭocblocks that listed arrays with multiple types weren’t interpreted correctly, causing a bunch of warnings about type mismatches between docblocks and PHP types. Array shapes with single quoted keys ( WI-65872)Īrray shapes weren’t properly detected when using single quoted strings as array keys, that’s fixed now. Our Xdebug integration had some issues not being about to show property information in several cases. Xdebug “Cannot get property” bugfix ( WI-65974) Some inspections marked code with a warning when they shouldn’t.
However, we didn’t properly detect the use of in some cases. PhpStorm supports type aliases in doc blocks that you can import and use in other places. In other words: values where the array_is_list function returns true. The list type, by the way, represents continuous, integer-indexed arrays. However, there were still some edge cases where the list notation wasn’t recognised by PhpStorm as a valid type. PhpStorm 2022.1 added support for multiline array shapes. List type in multiline array shapes ( WI-65260) PhpStorm 2022.1 had an issue with broken indices in some Magento projects, causing a Null Pointer Exception after indexing those projects. Fix index error in Magento projects ( WI-65276) PhpStorm however didn’t detect these changes in some cases when working with abstract classes. PHP allows you to change the visibility of any method or property to a less strict one during inheritance. Wrong visibility when changing visibility during inheritance ( WI-65245) However, this behavior didn’t work when the expression contained a string (which happens often). When changing a delimiter in a Twig file, PhpStorm will automatically change its corresponding opening and closing delimiter as well. Twig simultaneous delimeter’s editing ( WI-65400) We’ve made some improvements to how multiline arrays are auto formatted by PhpStorm. Multiline array formatting ( WI-61938, WI-65831) PhpStorm wasn’t able to correctly use rename refactoring combined with dynamic properties.
We now support Vite, the “ Next Generation Front End Tooling“! Rename dynamic fields ( WI-65177, WI-65840) However, when automatically generating a property via the constructor, PhpStorm didn’t set the correct visibility. PhpStorm allows you to define the default property visibility in Settings / Preferences | Editor | Code Style | PHP | Properties Default Visibility. The and directives within a directive weren’t properly formatted by PhpStorm. Let’s take a look! Improved blade formatting ( WI-37087) This release mainly brings a bunch of bug fixes and quality-of-life improvements. You can also download PhpStorm 2022.1.1 from the website. You can update to it using the Toolbox App or right from inside the IDE. The first minor update for PhpStorm 2022.1 is now available.
0 kommentar(er)
