Clojurians
#dirac
<
2017-11-19
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

sandbags17:11:13

@darwin Chrome Canary 64.0.3273.0, MacOS 10.12.6, Clojure 1.8.0, ClojureScript 1.9.946, dirac "RELEASE". Now I try it again I do notice a warning which is probably pertinent "We detected unexpected tools.nrepl library version in your nREPL server at <nrepl://localhost:8230>! The server reported version 0.2.12, but Dirac expected version 0.2.13"

sandbags17:11:26

i'm trying to figure out what is pulling in 0.2.12

darwin17:11:54

that should be fine in this case, don't worry about this

darwin17:11:06

there are not protocol differences between 0.2.12 and 0.2.13

sandbags17:11:45

then i saw no other warnings or messages

sandbags17:11:01

the thing worked in the sense that I could navigate to a .cljc file and set a breakpoint

sandbags17:11:05

and it stopped at the breakpoint

sandbags17:11:23

but it didn't show any of the locals in scope at that point and the stepping seemed a bit wonky

darwin17:11:57

did you try the same thing in internal devtools? was it better (minus names demangling)

sandbags17:11:19

i've no idea what you're asking me

sandbags17:11:27

what do you mean by "the same thing"

sandbags17:11:39

you mean setting a breakpoint in some JS code?

darwin17:11:51

did you try to set the same breakpoint in normal chrome devtools without using Dirac?

darwin17:11:23

please try the same workflow, just to check if you would see the locals you are expecting to see there

sandbags17:11:37

are you talking about CLJS and cljs scope or JS & js scope?

sandbags17:11:01

What I mean is, I am not sure what should be possible in the built-in devtools

sandbags17:11:11

i didn't think it could set breakpoints in CLJS code or inspect scopes

darwin17:11:39

you can, but you won't get some things dirac offers on top

sandbags17:11:41

also i guess that means i have to pull dirac out of my dependencies

darwin17:11:59

for example demangling clojurescript-generated variable names

darwin17:11:23

no, you don't have to pull dirac out, simply instead of dirac devtools open internal chrome devtools on your page

darwin17:11:02

since recent chrome releases they even work side by side, but better to close dirac devtools window and use the intenal (bundled) devtools

sandbags17:11:07

okay so chrome internal devtools seems to have the local scope variables

darwin17:11:52

ok, then something went wrong with dirac, I would need to see the code or maybe screenshots in the first step

darwin17:11:52

in the beginning I thought you placed the breakpoint to a wrong place where you expected locals but your were stopped "elsewhere" than expected

darwin17:11:16

using (js-debugger) should be precise, but using devtools UI could confuse real location

darwin17:11:53

because your clicks to set breakpoints go through source mapping somewhere into generated javascript code and you might hit some problematic spot

darwin17:11:42

please try to make two screenshots for me a) hitting the breakpoint in dirac devtools b) hitting it in the normal devtools

sandbags17:11:29

Ok. Can't do it now as I have to switch to some other work. But I'd be interested in having this work so next chance I get I will try and capture the two.

sandbags17:11:42

Thanks for taking an interest.

darwin17:11:52

ok, np, ping me here anytime