Mark Story
Mark Story
Not using `serialize()` may make expanding variable contents much harder as right now we rely on being able to traverse objects/arrays and generate the nested HTML structures. We wouldn't be...
We could keep max-depth shallow, like 3 or 4 levels, as a way to prevent slowdowns. I don't think we'd be able to use `Debugger::exportVar()` as is, because we'd still...
Not any time recently, but I agree the formatting isn't great.
I think the additions here are more directly related to the 'through' feature of BelongsToMany associations and the other page has similar examples, but not the same one. I'm in...
Thank you 🎉
In most applications the database name would be redundant as the connection generally maps to only one database. We could replace the connection name with the database name but having...
Query creation events will be the path of least resistance, as we already use events as a pattern. Is query object creation the important part? Is it useful to know...
We could, I am not sure we should though. Having debugkit disable authentication and authorization checks is risky as people often forget to disable debugkit in production. Perhaps we could...
That could work, I always worry about the person who accidentally leaves debug on in production. As it is cake not the user that gets blamed.
@Erwane That would be great!