This whole week has been about diving deep and figuring out a thorny question, one which was not answered in the Laravel documentation.
Yesterday, I shared a video demo of how I used Xdebug to figure some of this out.
But I wanted to end today with a broader principle that applies in general, not just to me: You can figure this out.
One of the things I enjoy about open source is that all the code is right there in my editor, even Laravel code or package code I import. None of it is a mystery, none of it is hidden.
Reading the official documentation is the most valuable thing you can do. But, I also realize that not every single scenario can be covered there. So you need an additional set of skills to figure it out on your own.
Learn how to navigate vendor code from your editor. Set up Xdebug when you need to go deep.
Do you want to customize Laravel's behavior? First study how it works with native functionality, and leverage those same patterns with your customization.
Everything you need is already there. It's just a matter of building the skill to find it.
Here to help,
Joel
P.S. And of course, if you're really stuck, there is no shame in asking for help either.