Damjan Cvetko

No sorry, not yet. There is still no feasible way to implement this and I'm currently dealing with cloud support.

Hi! You are right there were some changes in 1.20. The plugin tries to figure out where the PHP executable is. 1. It checks in the `launch.json` if `runtimeExecutable` is...

Hi @nickchomey. That is correct, they do have a conflict in this setting. I choose this setting but then later re-published PHP IntelliSense and just then realized that this causes...

I just started my day and can work on this after work. I do not have experience with Laragon... After installing 1.19 did the problems also stop? I think Intelephense...

Thanks for your feedback. I think I still need to change it as - it seems - two extensions can't offer the same setting. They can use the same setting,...

I'd suspect it has more to do with Laragon than either PHP IntelliSense or *Phence. I'll see if I can manage to test it, but since vanilla PHP works without...

Hi! The ignore directive matches against full path so adding `**/` as a prefix should help: ``` { "name": "Listen for Xdebug", "type": "php", "request": "launch", "port": 9003, "ignore": [...

Hm. It should work, but without the `log: true` I can't know for sure. If you attach it here I can maybe help you further. Could be a upper/lower case...

Hi @karmeljuk . This log is exactly what I needed. But I do not see a problem. There are lines where the debugger engine stops due to an exception, but...

I feel this should be responsibility of a different VS Code extension. You could also use `tasks.json`, I'm sure there is a way. Also, if possible, I strongly suggest VS...