Just like Blade, we have also been improving our Twig support. We plan to continue improving our Blade template engine support.

You can see the full list of fixed issues in our issue tracker.

WI-40358 Blade: inside block throws “Directive is not closed”.

WI-25667 Blade: formatting blocks are not aligning if there is a HTML comment after a closing tag.

WI-28285 Blade doesn’t indent nested statements when formatting.

WI-31196 Blade: wrong formatting with HTML comments.

WI-64463 Blade: two consecutive fragments are merged together and produce “expected: expression” warning.

WI-64460 Blade: missing completion for methods inside tags if there is php block ().

WI-37741 AutoCompletion of PHP Variables in Blade.

Many other issues with code completion and formatting in Blade templates were resolved as well, including: You can now also import namespaces in your blade files, instead of always having to use FQCNs: As the result, you’ll get much better code completion in your Blade files: Namespace imports with autocompletion Nu các bn dùng key không c có th active phpstorm, webstorm qua license server hoc reset thi gian dùng th JetBrains IDEs nhé, hin ti mình cng ang dùng license server và ang work bình thng. In PhpStorm 2022.1, we’ve significantly reworked how the IDE handles Blade templates. It caused many issues, such as losing code completion: Previously, PhpStorm treated every code block in Blade templates as an independent scope.

Better psalm and generic annotation support.

Improved support for autocompletion in Blade templates.

Let’s dive in! What’s new? Frameworks and languages You can download PhpStorm 2022.1 here and read through this post to learn about all the new features and improvements inside. This new major PhpStorm release includes improved Blade and Twig support, added functionality to docblock type annotations and attributes, a bunch of new and useful inspections, several improvements to the editor, and more.

Phpstorm idea license server