This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-26
Channels
- # admin-announcements (2)
- # aws (1)
- # beginners (21)
- # boot (61)
- # cider (5)
- # cljs-dev (94)
- # cljsrn (35)
- # clojure (106)
- # clojure-austin (3)
- # clojure-belgium (1)
- # clojure-dev (4)
- # clojure-dusseldorf (9)
- # clojure-greece (2)
- # clojure-mexico (1)
- # clojure-russia (40)
- # clojure-spec (61)
- # clojure-uk (17)
- # clojurescript (151)
- # code-art (1)
- # component (7)
- # core-async (4)
- # cursive (1)
- # datomic (9)
- # dirac (55)
- # funcool (12)
- # hoplon (118)
- # incanter (12)
- # jobs (8)
- # juxt (1)
- # lein-figwheel (6)
- # mount (2)
- # off-topic (2)
- # om (76)
- # onyx (28)
- # other-lisps (1)
- # planck (7)
- # re-frame (9)
- # reagent (13)
- # ring-swagger (2)
- # specter (1)
- # yada (22)
@vikeri: it's definitely better with boot-react-native, as it just runs the regular cljs compiler in a terminal
although there's still a lot of room for improvement there
I’m usually run lein prod-build
and see compile errors:smile:
I use audible feedback, so you get a "chime" sound if compilation worked, "3 warnings" if there were warnings
though it doesn't catch syntax errors, weirdly
@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.
it'd be great for everyone to work together to improve error reporting
there's a nice momentum at the moment in the community to improve these things (see clojure.spec)
Yes, I am a little troubled by the fragmentation in lein vs boot though. Would be nice to settle on one.
I think competition is healthy, but for some things I think it is better to have one standard.
yeah they both have their pros
I converted to boot some time ago and like it a lot
especially for this type of use case (like cljsrn) it's ideal, as you can do multiple things at once
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.
I know we haven't done a good job improving boot-react-native so far. It's particularly hard to get started
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
one thing that is great is that brn integrates with RN's packager directly, so you get all its features
including pretty fast reloading, requiring images just works
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.
yeah there's lots of overlap
all the RN npm libraries that need to be wrapped, for example
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.
Maybe better create new repo on github and in issues accumulate all ideas?
@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?
@drapanjanas: No nothing, I was using an anonymous function # in map and when I changed it to a normal fn it worked
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
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?
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
This is the code snippet: http://pastie.org/private/o36mipkezxxxlhr1ovyxa
@debug, I think you need to wrap the result of the render fn in as-element
as in :renderRow #(r/as-element [text (pr-str (js->clj % :keywordize-keys true))])