This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-07
Channels
- # aleph (15)
- # beginners (18)
- # boot (18)
- # business (1)
- # cider (11)
- # cljs-dev (13)
- # cljsrn (19)
- # clojure (14)
- # clojure-austin (8)
- # clojure-dusseldorf (1)
- # clojure-finland (1)
- # clojure-greece (118)
- # clojure-poland (3)
- # clojure-russia (46)
- # clojure-spec (65)
- # clojure-uk (18)
- # clojurebridge (3)
- # clojurescript (16)
- # cloverage (7)
- # core-async (8)
- # cursive (74)
- # datomic (28)
- # editors (3)
- # emacs (3)
- # ethereum (5)
- # hoplon (19)
- # jobs-rus (18)
- # lein-figwheel (1)
- # off-topic (2)
- # om (107)
- # om-next (4)
- # onyx (23)
- # pedestal (23)
- # proton (3)
- # protorepl (1)
- # re-frame (108)
- # reagent (10)
- # ring-swagger (15)
- # spacemacs (2)
- # specter (11)
- # testing (7)
- # untangled (79)
- # vim (4)
- # yada (53)
https://github.com/cursive-ide/cursive/issues/1557 Cursive and Reagent users 👍 if this would be useful for you
@borkdude thanks for explaining
When using devcards with reagent, I have to reload the page after causing exceptions
The JS exception displays properly. But after I fix the bug, the page doesn't fix itself; instead I see "react.inc.js:5915 Uncaught TypeError: Cannot read property '_currentElement' of null"
N.b. this is with runtime exceptions (e.g. asserts), not with syntax errors (which are displayed corectly)
I think it's something to do with unmounting components
looks like this issue: https://github.com/facebook/react/issues/4026
"React currently cannot recover from an error inside render."
That's both surprising and annoying