This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-20
Channels
- # admin-announcements (5)
- # alda (1)
- # aws-lambda (1)
- # beginners (74)
- # boot (62)
- # cider (29)
- # cljs-dev (36)
- # cljsjs (15)
- # cljsrn (34)
- # clojure (58)
- # clojure-android (3)
- # clojure-austin (15)
- # clojure-austria (11)
- # clojure-dusseldorf (25)
- # clojure-germany (6)
- # clojure-greece (26)
- # clojure-quebec (8)
- # clojure-russia (50)
- # clojure-spec (12)
- # clojure-uk (8)
- # clojurescript (46)
- # core-async (11)
- # cursive (22)
- # datomic (2)
- # devcards (27)
- # dirac (5)
- # hoplon (109)
- # jobs (1)
- # kekkonen (2)
- # lein-figwheel (12)
- # leiningen (2)
- # microservices (1)
- # off-topic (3)
- # om (70)
- # onyx (17)
- # planck (21)
- # re-frame (3)
- # reagent (2)
- # rum (1)
- # spacemacs (12)
- # spirituality-ethics (9)
- # untangled (44)
- # vim (2)
- # yada (8)
@pvinis: not sure anyway, I’m feel comfortable with rn and cljs)
Are you using re-natal? If so, maybe you need to enable the source maps? re-natal enable-source-maps
Has anyone looked into using IntelliJ + Cursive for cljsrn debugging? It looks like it supports remote debugging. I don’t really understand how everything is wired up w/r/t react native, so this may be a stupid question. https://www.jetbrains.com/help/idea/2016.1/debugging-javascript.html?origin=old_help
@pvinis: what do you mean?
I don’t think so. Figwheel is automatically reloading any changed cljs files.
@macroz: looks like it common trouble) we find that cljs-ajax not work as expected on RN and then using js/fetch
for ajax
cljs-ajax seems to work as expected, the resulting code is executed, but the printing seems not to be captured by figwheel
when I record something in the callback to e.g. an atom, the result is visible after the callback is called
@macroz: are you use enable-console-print!
?
no, but that does not seem to have any effect, also println works just fine in the REPL without it
@macroz: in code you need to use enable-console-print!
to use print
, in repl you don’t need this
but e.g. POSTing from REPL with cljs-ajax and then printing in the callback does not work, the output goes somewhere else
@seantempesta: I’m also developing in Cursive, hence very interested in the subject. Since you can connect Atom as a debugger instead of Chrome it should be possible. But as you said, RN is sort of a jungle still in some of these more ”advanced” topics. Watched a very interesting talk about profiling but then nothing of it was documented anywhere and the methods he showed on screen were nowhere to be found.
@seantempesta: Are you getting runtime errors with references to cljs code with re-natal btw? Or just compile time errors?
@vikeri: Ha. Both of course. My programming style is kind of a stumble around with a flashlight in the dark approach.
I just think it’d be sweet to debug everything from the Cursive REPL.