5 ms·
> when it goes wrong you find yourself sifting through OOP-obfuscated layers of framework and libraries just to find out how exactly your controller is called.
by irobeth 3y ago
> when it goes wrong you find yourself sifting through OOP-obfuscated layers of framework and libraries just to find out how exactly your controller is called.
debug_backtrace() has always been my friend in situations like this
- nine_k 3y agoIndeed so. But there's value in an ability to find out such things without running the code, just by looking at it.