Kirby, mamp, xdebug and sublime

i am using mamp pro on my mac and would love to do some debugging right out of sublime text using a plugin. but… xdebug stops at halt_level notice as well and kirby creates a few of them. which is fine in general but to track my error i do not want to run a few times and having some lib files opend just to reach my breakpoint.

so how to solve this? RTFM on how to configure the plugin.

Sublimetext > Prefrences > Package Settings > xdebug > Settings – User then add this line to the existing code. Notice the missing Notice (pun intended).

"break_on_exception": ["Fatal error", "Catchable fatal error", "Warning", "Parse error", "Strict standards", "Deprecated", "Xdebug", "Unknown error"]

+1 when using xdebug on vscode i am also having to jump between many warnings before actually debugging my file…

such as when using the filterBy function and not using all arguments it’ll throw that as a breakpoint…

seems like they have it build in on the debug sidebar where you can just enable/disable at what kind of things the debugger should stop…

php_-carbul-_Visual_Studio_Code_2017-10-13_17-18-25