Now you’re ready to begin step debugging! blade.php extension, just like you would with PHP files. Having done all that, you can set a breakpoint in the original Blade template files with a. Configure PhpStorm for Blade debugging by specifying a path to the compiled templates under Settings/Preferences | Languages & Frameworks | PHP | Debug | Templates.Check out the Ultimate Guide on Debugging or this quickstart video on debugging with Docker. To start debugging Laravel Blade templates: Fortunately, this is not a problem anymore. Putting a breakpoint in the compiled file was tough. So before PhpStorm 2019.1, if you set a breakpoint in an original Blade template, it would never stop there. Then the application runs those compiled files. First, they are compiled and saved to a cache directory. The problem is that Blade templates are not the files that your application runs.
Combined with PhpStorm 2019.1 this small change gives an awesome new feature: now you’ll be able to do step debugging inside of original Blade files! Laravel 5.8 has just been released! Among other features, it delivers a small template modification. Or, if you have the previous PhpStorm 2019.1 EAP build installed, you will soon get a notification in the IDE about a patch update. You can download it on the website or via JetBrains Toolbox App. This build delivers support for debugging Laravel 5.8 Blade templates, improvements and fixes for PHP, and all the fresh updates from the WebStorm team and IntelliJ Platform!
0 kommentar(er)
