This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-10
Channels
- # announcements (15)
- # bangalore-clj (1)
- # beginners (207)
- # calva (22)
- # cider (4)
- # clara (73)
- # cljs-dev (7)
- # cljsrn (4)
- # clojure (125)
- # clojure-dev (38)
- # clojure-europe (2)
- # clojure-india (11)
- # clojure-italy (11)
- # clojure-nl (14)
- # clojure-russia (22)
- # clojure-uk (32)
- # clojurescript (30)
- # cursive (11)
- # datavis (2)
- # datomic (14)
- # editors (3)
- # emacs (3)
- # hyperfiddle (4)
- # juxt (13)
- # klipse (1)
- # luminus (5)
- # nrepl (7)
- # off-topic (9)
- # overtone (13)
- # portkey (1)
- # re-frame (15)
- # reagent (13)
- # ring (30)
- # schema (4)
- # shadow-cljs (108)
- # spacemacs (8)
- # specter (3)
- # sql (2)
- # testing (11)
- # tools-deps (21)
- # unrepl (4)
@henrik One thing you can do is use this macro to get a string with that in the output: https://github.com/weavejester/hiccup/blob/master/src/hiccup/page.clj#L61-L75
Finally using reagent in anger. Many thanks to everyone involved in the project, writing blog posts etc — it’s been fantastic!
I learned about the “in anger” expression from https://www.youtube.com/watch?v=8o01g6C7jWg
Interesting that nolen uses reagent in his demo, I thought he was the maintainer of the "competition"
Has someone ever experienced this error before?
Warning: unmountComponentAtNode(): The node you're attempting to unmount was rendered by another copy of React.
Uncaught Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
at invariant (react-dom.development.js:56)
at scheduleWork (react-dom.development.js:18407)
at captureCommitPhaseError (react-dom.development.js:18159)
at commitRoot (react-dom.development.js:17400)
at completeRoot (react-dom.development.js:18913)
at performWorkOnRoot (react-dom.development.js:18842)
at performWork (react-dom.development.js:18750)
at requestWork (react-dom.development.js:18724)
at scheduleWork (react-dom.development.js:18402)
at updateContainerAtExpirationTime (react-dom.development.js:19070)
This happens when your application reloads, but only partially with some component being left out so when the reload happens they are in fact two different instances. I had this happening to me with re-frame-10x being in a window by itself and since it's a separate window it doesn't get reloaded.
I think I remember a recent conversation where someone did lein deps :tree
and found they had 2 diff versions of React installed (one pulled in as a dependency of some other lib). Might be related to the “another copy of React” bit, though I don’t know about the “maximum update depth” part.