Usually, if I start the debugger for other programming languages like Java or Go it's working right from the beginning - sometimes without even any configuration needed at all.ĭisclaimer: This is just me speaking about my experience. Maybe it's me, maybe my process of thinking is just not compatible with the way Xdebug is working.But I know I'm not alone. I'd say I'm a quite seniorish developer and I work with PHP for like 20 years - but until today Xdebug and me never developed a friendship. Now that you understand how to go about debugging a single PHP script, what might the process of debugging a typical Laravel application look like Download this video. Is it the server XDebug configuration? Is it some port mapping issue? Something with Docker/Vagrant/VirtualBox? Is something wrongly configured in the IDE? Hard to find out if you don't have any hints. Additionally, if it's not working, you don't immediately know where to start searching for the issue.
For sure we missed something, but the amount of different configuration options makes it hard to set up in my eyes. Even for the same project - if it was working for me - it wasn't for a collegaue - even if we compared settings. L aravel offers some good tools for debugging and for many cases this may be enough but if it gets choppy, a real debugger is simply unbeatable. If I want to set it up for a new project I almost always struggle - what means I have to google around, compare configs, try this and that in my IDE and php.ini until it finally works and I don't exactly know why.
0 kommentar(er)
