This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-04
Channels
- # beginners (14)
- # boot (28)
- # chestnut (9)
- # cljsrn (18)
- # clojure (64)
- # clojure-conj (1)
- # clojure-dusseldorf (45)
- # clojure-finland (4)
- # clojure-gamedev (1)
- # clojure-greece (8)
- # clojure-italy (22)
- # clojure-russia (4)
- # clojure-spec (19)
- # clojure-uk (38)
- # clojurescript (49)
- # code-reviews (2)
- # component (12)
- # core-async (3)
- # cursive (3)
- # data-science (2)
- # events (4)
- # fulcro (394)
- # heroku (3)
- # hoplon (16)
- # immutant (11)
- # jobs (5)
- # lein-figwheel (1)
- # lumo (18)
- # off-topic (8)
- # om (11)
- # other-languages (1)
- # overtone (1)
- # pedestal (7)
- # portkey (62)
- # protorepl (1)
- # re-frame (40)
- # reagent (41)
- # ring-swagger (5)
- # spacemacs (5)
- # unrepl (5)
- # yada (12)
has anyone hit https://github.com/bhauman/lein-figwheel/issues/596 trying to upgrade to figwheel 5.13 so I can use re-frisk 0.5.0
@sllyq I think that is reagent
way of dealing with components declared as JS classes. Otherwise you are forced to do something like (r/adapt-react-class (.-Text ReactNative))
Because sometimes thing in my app stop working and oftentimes without good indication of what's wrong
@sllyq yeah getting better errors is a struggle
try the following
1. check the debug log religiously ("react-native log-ios"). It should have at least the exception name
2. you could try the Chrome debugger mode (I don't use it personally)
3. check Figwheel's log (`tail -f figwheel_server.log`) for compiler errors. These don't get as much visibility as on the web. If a namespace doesn't compile and you reload without fixing, things can break pretty thoroughly. Best to go back to a version that compiles and retrace your steps. Always react to compiler errors immediately
4. restart figwheel to surface compiler errors. Sometimes a ns didn't compile without errors, but subsequent compiles won't show the error again. You'll need to restart figwheel and check for any errors and warnings
5. no tolerance for warnings! Fix them
6. errors in render fns are particularly annoying because they break hot reloading. You'll need to reload using Command-R
7. try some tricks I've used to get better error messages in render fns and better stacktraces (the default Red Screens are unfortunately not too helpful without source maps): https://gist.github.com/pesterhazy/e6846be1b6712a9038537022d131ce46
8. finally the standard rules of working with cutting edge tech apply: checkpoint in version control at every known-good point, force yourself to make baby steps so you know what caused breakage, and question your assumptions about how things work, especially when things break