Fork me on GitHub
#cljsrn
<
2016-06-20
>
pvinis08:06:01

i think i might go with js rn.. i feel that the cljs rn is not ready yet..

pvinis08:06:35

and when i stumble on something, debugging it feels awkward

savelichalex08:06:24

@pvinis: not sure anyway, I’m feel comfortable with rn and cljs)

pvinis09:06:54

nice. thats good. i will be trying again soon. i hope i can figure it out 😄

pvinis11:06:31

is there a way to debug in chrome with cljsrn?

pvinis11:06:53

because i cant seem to be able to find the cljs sources

seantempesta11:06:29

Are you using re-natal? If so, maybe you need to enable the source maps? re-natal enable-source-maps

pvinis11:06:28

didnt see that before

seantempesta11:06:35

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

pvinis11:06:29

with re-natal, when using figwheel, is there a reason to have hot reloading enabled?

savelichalex11:06:23

@pvinis: what do you mean?

pvinis12:06:30

i mean with cmd+D

pvinis12:06:41

you can enable live reload, and also hot reload

pvinis12:06:00

but is there actually a reason why i should have them enabled?

pvinis12:06:08

becasue figwheel already reloads

seantempesta12:06:03

I don’t think so. Figwheel is automatically reloading any changed cljs files.

Macroz12:06:02

Maybe this belongs to #C0E1SN0NM

savelichalex13:06:04

@macroz: looks like it common trouble) we find that cljs-ajax not work as expected on RN and then using js/fetch for ajax

Macroz13:06:21

cljs-ajax seems to work as expected, the resulting code is executed, but the printing seems not to be captured by figwheel

Macroz13:06:00

when I record something in the callback to e.g. an atom, the result is visible after the callback is called

savelichalex13:06:24

@macroz: are you use enable-console-print!?

Macroz13:06:39

no, but that does not seem to have any effect, also println works just fine in the REPL without it

savelichalex14:06:42

@macroz: in code you need to use enable-console-print! to use print, in repl you don’t need this

Macroz14:06:33

yes but that has no effect whatsoever

Macroz14:06:55

console printing perhaps goes to the debug console somewhere

Macroz14:06:08

so calling a function that prints works

Macroz14:06:13

(from REPL)

Macroz14:06:43

but e.g. POSTing from REPL with cljs-ajax and then printing in the callback does not work, the output goes somewhere else

vikeri16:06:18

@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.

vikeri16:06:54

@seantempesta: Are you getting runtime errors with references to cljs code with re-natal btw? Or just compile time errors?

seantempesta23:06:46

@vikeri: Ha. Both of course. My programming style is kind of a stumble around with a flashlight in the dark approach.

seantempesta23:06:23

I just think it’d be sweet to debug everything from the Cursive REPL.