You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine that you must work with a code of another person. There is a view with multiple partials and you wish to check in which one of them and at what line a query is triggered. With Query Tracer it is simple, as you see the cached template file name and specific line. You cannot do this so fast when seeing only a "Template file" information:
Barry is not sure about the usefulness of showing a name of cached template, instead of a real name. But for debugging purpose it is enough to see the cached template name - it is the same in the stack trace. Certainly it is better than seeing nothing.
Thanks for the debugbar (and the "backtrace" option), I cannot live without it.
The text was updated successfully, but these errors were encountered:
Hi
Related to discussion: https://mobile.twitter.com/laravelnews/status/732550470149902336
(I'm posting this to allow eventual further discussion, as twitter is not a good place for this, and to have an explanation of a future pull request).
Imagine that you must work with a code of another person. There is a view with multiple partials and you wish to check in which one of them and at what line a query is triggered. With Query Tracer it is simple, as you see the cached template file name and specific line. You cannot do this so fast when seeing only a "Template file" information:
Barry is not sure about the usefulness of showing a name of cached template, instead of a real name. But for debugging purpose it is enough to see the cached template name - it is the same in the stack trace. Certainly it is better than seeing nothing.
Thanks for the debugbar (and the "backtrace" option), I cannot live without it.
The text was updated successfully, but these errors were encountered: