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
@Malabarba nREPL already does the equivalent of pr-str on :value slots in responses (see this middleware), so I think we're double-printing. This likely only happens with more recent versions of nREPL (>= 0.27) due to a change in the middleware ordering algorithm in 0.2.7. We have a few options:
Include a non-nil value in the :printed-value slot of the response, so pr-values will skip printing
Keep doing the printing ourselves in the debugger middleware but use a different slot name than :value
Remove the call to pr-str from the debugger middleware, and add #'pr-values to the :requires set of wrap-debug, to guarantee that the slot will be printed (like here)
:printed-value was only added to nREPL 0.2.10, and pr-values is technically an nREPL implementation detail, so maybe option 2 is the simplest. Thoughts?
I added the manual printing because it seemed to be necessary on the
nrepl version I had. Otherwise I ran into issues. I think my version
was 0.2.6, so it's consistent with what you're saying, @cichli.
Consider an example:
I want to debug the following call to 'foo:
Debugger step results as I press "n":
The text was updated successfully, but these errors were encountered: