PHPstorm-无法在blade.php文件中设置断点-PHPstorm-Unabletosetbreakpointsinblade.phpfiles

39  

Putting a

放一个

into your blade file works pretty well. Even in my tests, PHPstorm jumps to the next PHP statement in some cases.

进入你的刀片文件工作得很好。即使在我的测试中，PHPstorm在某些情况下会跳转到下一个PHP语句。

Why this works:

为何如此有效：

Laravel processes the blade file to a normal PHP file in the cache folder. But the PHP statement xdebug_break(); will be transferred there and cause the program to halt at the position you want it to (in the cache file).

Laravel将刀片文件处理为缓存文件夹中的普通PHP文件。但PHP语句xdebug_break（）;将被转移并导致程序在您想要的位置停止（在缓存文件中）。

3  

To close this question - phpstorm doesnt support this functionality at the moment. A work around provided by jetbrains support was to add *.blade.php to file type associations under PHP in the IDE settings, however, it still wasnt working for me after doing this.

要关闭这个问题 - 目前phpstorm不支持​​此功能。由jetbrains支持提供的解决方法是在IDE设置中将* .blade.php添加到PHP下的文件类型关联，但是，在执行此操作后它仍然不适合我。

It appears that they created a youtrack ticket in response to my request, if youd like to encourage jetbrains to work on this please upvote: youtrack.jetbrains.com/issue/WI-26476

看来他们根据我的要求创建了一张跟踪票，如果你想鼓励喷气机使用这个请购买：youtrack.jetbrains.com/issue/WI-26476

2  

Even if you can get the IDE to enable breakpoints on the blade files, it won't work - Laravel composes a PHP file from the Blade file - it is this file that is eventually used when the script is run - not the Blade file.

即使您可以让IDE在刀片文件上启用断点，它也无法工作 - Laravel从Blade文件编写一个PHP文件 - 这个文件最终在脚本运行时使用 - 而不是Blade文件。

A Work-Around

解决方法

This works for PHPStorm - but something similar might be possible in other IDEs.

这适用于PHPStorm - 但在其他IDE中可能有类似的东西。

Laravel (5) stores the composed files under storage/framework/views. These files have random generated file names - so it may be tricky to find the file you want. An easy way is to delete all these temp files and then refresh the page you want to debug. A new file will be created. In PHPstorm you can right-click on the file and select the file's extension type. (Not sure about other IDEs)

Laravel（5）将组合文件存储在storage / framework / views下。这些文件具有随机生成的文件名 - 因此找到所需的文件可能很棘手。一种简单的方法是删除所有这些临时文件，然后刷新要调试的页面。将创建一个新文件。在PHPstorm中，您可以右键单击该文件并选择文件的扩展名类型。 （不确定其他IDE）

You will now be able to set breakpoints. Obviously you will need to make the changes in the Blade file - but this will at least help you to figure out what is wrong.

您现在可以设置断点。显然，您需要在Blade文件中进行更改 - 但这至少可以帮助您找出问题所在。

**Update: Alex's solution is easier! **

**更新：Alex的解决方案更容易！ **

0  

I devised an even better hack, which allows conditional debugging support, so that you aren't stuck with XDebug_break for the rest of eternity.

我设计了一个更好的黑客，它允许条件调试支持，这样你就不会在永恒的剩余时间里坚持使用XDebug_break。

The single line expands as follows.

单行扩展如下。

This statement has a couple of unusual features.

该声明有几个不寻常的功能。

1. Since blade files done't have use directives, the method name, \app\utils\DebugLogger::EnableForBlades is fully qualified.
2. 由于刀片文件没有使用指令，因此方法名称\ app \ utils \ DebugLogger :: EnableForBlades是完全限定的。
3. Since blade files seem to lack support for the usual code blocking mechanism, the one-line statement is devoid of braces, and is terminated by a semicolon.
4. 由于刀片文件似乎缺乏对通常的代码阻塞机制的支持，因此单行语句没有大括号，并以分号结束。

EnableForBlades is a static method that queries an environment variable (one of those defined in .local.env), returning True if that variable evaluates to True. Otherwise, it returns False, and xdebug_break is suppressed.

EnableForBlades是一个静态方法，用于查询环境变量（在.local.env中定义的变量之一），如果该变量的计算结果为True，则返回True。否则，它返回False，并禁止xdebug_break。