Replies: 2 comments 1 reply
-
Ping ... any ideas on this? Thank you! |
Beta Was this translation helpful? Give feedback.
1 reply
-
OK, thank you, I will try to take a look once I have some time available
(it may be 2-3 weeks before I get around to this).
…On Mon, Apr 25, 2022 at 12:59 PM Freek Van der Herten < ***@***.***> wrote:
Hi!
Because you're the only one requesting this, we're currently not investing
time in this feature.
Should it be easy to add easily, feel free to send us a PR with tests and
updated docs.
—
Reply to this email directly, view it on GitHub
<#677 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACT4PRCJVHYMMFMG3SLFW3VGZ3HDANCNFSM5TN6B4MQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Let me prefix this by saying that I would understand if your reply will be "not an issue, won't fix" ...
Let me explain: I'm in the process of refactoring/upgrading a large legacy application that is making heavy use of Ajax calls ... ray is proving to be a life-saver here, so thank you for that.
My issue is this: our architect has demanded that we wrap the ray() call in a simple debug wrapper (not unreasonable since this wrapper contains a number of other useful debug-related methods) which now means that instead of "ray()" we call "Debug::ray()" ... this works just fine, but the result is that the location of the ray call is now always displayed as "Debug.php:123" rather than the actual line where the call is to "Debug::ray()" is placed.
Is there any way to tell ray to show not the top item from the stack trace but the top-minus-1 line from the stack trace so that the ray output would show where the actual call was placed?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions