This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-07
Channels
- # adventofcode (269)
- # beginners (100)
- # boot (6)
- # cider (4)
- # cljsrn (4)
- # clojure (161)
- # clojure-android (31)
- # clojure-argentina (2)
- # clojure-brasil (8)
- # clojure-greece (45)
- # clojure-india (2)
- # clojure-madison (2)
- # clojure-russia (17)
- # clojure-spec (4)
- # clojure-sweden (1)
- # clojure-uk (32)
- # clojurescript (93)
- # core-logic (2)
- # cursive (21)
- # data-science (2)
- # datomic (46)
- # defnpodcast (1)
- # duct (5)
- # emacs (21)
- # events (1)
- # fulcro (17)
- # graphql (13)
- # job (1)
- # jobs (2)
- # leiningen (11)
- # lumo (3)
- # off-topic (119)
- # om (4)
- # onyx (2)
- # planck (6)
- # portkey (12)
- # re-frame (5)
- # reagent (3)
- # ring (5)
- # shadow-cljs (27)
- # spacemacs (19)
- # specter (6)
- # unrepl (9)
@peeja Haven't tested but there is a commit React 16 support anmonteiro committed on Sep 29
@peeja FYI when I ported Fulcro away from Om Next, I noticed that that code is broken under adv opt
It is trying to track “mounted” status…using the lifecycle hooks via the defui wrapping works better.
If anyone wanted to back-port the fix, it is here: https://github.com/fulcrologic/fulcro/blob/v2.0.0-beta5/src/main/fulcro/client/primitives.cljc#L396 Just look for anything related to fulcro$mounted
…should be fairly easy. Remove the stuff in Om next about react fibre and such for this same concern.