Fork me on GitHub
#cljsrn
<
2016-05-26
>
pesterhazy13:05:56

@vikeri: it's definitely better with boot-react-native, as it just runs the regular cljs compiler in a terminal

pesterhazy13:05:21

although there's still a lot of room for improvement there

savelichalex13:05:42

I’m usually run lein prod-build and see compile errors:smile:

pesterhazy13:05:01

I use audible feedback, so you get a "chime" sound if compilation worked, "3 warnings" if there were warnings

pesterhazy13:05:17

though it doesn't catch syntax errors, weirdly

vikeri13:05:11

@pesterhazy: Ok, interesting that you get better errors with boot-react-native. I have source maps enabled for re-natal but they don’t do me much favor here though… @savelichalex: Alright, not ideal but a good way to catch the errors.

pesterhazy13:05:33

it'd be great for everyone to work together to improve error reporting

pesterhazy13:05:54

there's a nice momentum at the moment in the community to improve these things (see clojure.spec)

vikeri13:05:18

Yes, I am a little troubled by the fragmentation in lein vs boot though. Would be nice to settle on one.

vikeri13:05:44

I think competition is healthy, but for some things I think it is better to have one standard.

pesterhazy13:05:57

yeah they both have their pros

pesterhazy13:05:20

I converted to boot some time ago and like it a lot

pesterhazy13:05:41

especially for this type of use case (like cljsrn) it's ideal, as you can do multiple things at once

vikeri13:05:48

Ok, yeah I haven’t used it much, but I started my RN exploration with it. What are your general opinions on the pros and cons? But I found re-natal to be much more stable and ”just work” out of the box. So I settled for it. Not saying I won’t switch if the arguments are compelling. Better error messages is one.

pesterhazy13:05:34

I know we haven't done a good job improving boot-react-native so far. It's particularly hard to get started

pesterhazy13:05:12

Also haven't update in a while. I'm actually updating our stack to RN 0.26, so maybe we can do a release when that's done? cc: @mjmeintjes

pesterhazy13:05:56

one thing that is great is that brn integrates with RN's packager directly, so you get all its features

pesterhazy13:05:26

including pretty fast reloading, requiring images just works

vikeri13:05:32

Sounds good, I don’t think the reload is slow on re-natal though. I had a discussion about maybe joining the forces between re-natal and boot-react-native in a common lib. Share lein templates for example. And other RN-scripts if possible.

pesterhazy13:05:00

yeah there's lots of overlap

pesterhazy13:05:24

all the RN npm libraries that need to be wrapped, for example

vikeri13:05:37

Exactly, when people start to have proper tests I guess it would be pretty neat to have that working agnostically for boot/lein as well.

savelichalex13:05:34

Maybe better create new repo on github and in issues accumulate all ideas?

drapanjanas13:05:36

@vikeri about that error message, were you able find out what was wrong? I mean was it a compile problem or smth else? Figwheel usually reports of compile problems and you should see a yellow box containing messgae. Wasnt that te case?

vikeri13:05:11

@drapanjanas: No nothing, I was using an anonymous function # in map and when I changed it to a normal fn it worked

pesterhazy13:05:34

Has anyone had experience with using the latest React Native with boot-react-native? I'm running into this issue: https://github.com/mjmeintjes/boot-react-native/issues/49 -- I'm guessing because of change in the RN packager

drapanjanas13:05:00

Hmm.. then I guess it was a runtime error. I guess the biggest problem here is that in stack trace you do not see any calls from your code but some other stuff . Otherwise source maps would help right?

vikeri13:05:02

Exactly, I don’t think I ever saw a reference to my code in an RN error message actually. As in filename.cljs L:linenumber

debug18:05:20

Just starting out with re-frame / reagent and trying to make a ListView work

debug18:05:45

Getting a message that says "Invalid arity: 1"

debug18:05:11

What could be the problem?

debug18:05:39

Any recommendation and tips highly appreciated

pesterhazy18:05:39

@debug, I think you need to wrap the result of the render fn in as-element

pesterhazy18:05:29

as in :renderRow #(r/as-element [text (pr-str (js->clj % :keywordize-keys true))])