This repository has been archived by the owner on Mar 12, 2023. It is now read-only.
[BUG] Can not step into subsequent calls on the same line of code (only the call which is evaluated first by Ruby) #75
Labels
bug
Something isn't working
Describe the bug
Given code such as:
it is not apparently possible to step into the
foo
call. When Jard stops on this line,Step
will step into the#to_h
call. Unlike something likebyebug
,Step Out
does not take me back to thefoo(bar.to_h)
line but appears to step up/out past it or perhaps just steps over it (it's hard to tell).To Reproduce
Enter

jard
before a method call that contains arguments which need evaluation via a method call. For instance:F7
will take you to the first evaluated method call (request.referrer
orrequest
, depending on whetherrequest
is a local var or a method)Shift+F7
will take you to line after the initial break point (or a frame higher, if the breakpoint was the last line.Expected behavior
There should be someway step into
redirect_to
(and any other calls on that break point). For instance,byebug
(andpry-byebug
) you could dostep
,up
,step
,up
,step
and you would be insideredirect_to
. It's clumsy, but it works.Ideally,
jard
would underline the call which it would next step into, but admittedly that may be impossible to do reliably. However, it would look something like:I am pretty confident this is not possible without some pretty advanced static analysis, but it does at least illustrate the steps that are expected to be able to be taken manually.
Screenshots
(inline in reproduction steps)
Environment (please complete the following information):
tput colors
in your terminal: 256echo $TERM
in your terminal: xterm-256colorstty
:The text was updated successfully, but these errors were encountered: