TIL about xrDebug. Am I the only one who finds it weird that someone would create a debugger for #php that uses an extremely minor variation in name of the popular #xDebug extension?
I'd say, every professional developer used @Xdebug in one or the other way in their work. But debugging Neos or Flow applications can be challenging, since Flow generates proxy classes in a different directory than the original class. @derickr kindly created a proof of concept for supporting our case in Xdebug. Now we are raising funds to make it really happen, and we almost reached our goal: https://www.flownative.com/en/blog/flow-support-for-xdebug.html
OH @derickr at #sfugberlin "Turns out hyperlinking from #xdebug error messages right to the explanation in the documentation helps reducing support request mails - a lot"
Some time ago I had to develop a feature for a Neos CMS project and wanted to use @Xdebug - as I always do it in our @ddev projects. But it turned out to need a bit more configuration.
I finally wrote a blog post about why Neos CMS is different from other PHP software and how I managed to use Xdebug almost the way I'm used to.
Something that is really nice about using #PHP as a templating language (instead of Twig, Blade or whatever) is that you can easily debug templates using #XDebug.
Today @Xdebug helped me to locate a bug introduced by a stupid typo by me in a configuration file. My brain parser failed to detect that typo. Nevertheless it took me way too long to eventually hunt down the error.
Big kudos for this great tool! #xdebug