
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 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.
