This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-01
Channels
- # admin-announcements (2)
- # aleph (1)
- # aws-lambda (14)
- # beginners (6)
- # boot (34)
- # carry (71)
- # cider (8)
- # cljs-dev (3)
- # cljsjs (3)
- # clojure (40)
- # clojure-belgium (1)
- # clojure-greece (182)
- # clojure-mexico (1)
- # clojure-poland (8)
- # clojure-quebec (1)
- # clojure-russia (72)
- # clojure-spec (30)
- # clojure-uk (120)
- # clojurescript (62)
- # cursive (3)
- # datomic (17)
- # euroclojure (5)
- # hoplon (26)
- # keechma (6)
- # mount (3)
- # off-topic (2)
- # om (5)
- # onyx (4)
- # other-languages (3)
- # parinfer (2)
- # pedestal (2)
- # planck (30)
- # re-frame (81)
- # reagent (31)
- # spacemacs (7)
- # spirituality-ethics (21)
- # testing (10)
- # untangled (80)
Just heads up, if you are using ring-transit, then to save 24+ hours of your life to rather use the middleware.clj for wrap-transit-respone middleware from Anmonteiro. Because ring-transit is broken and wont show you the transit request from the backend.
yeah, if you’re using transit you should use Om Next’s writer and reader, as they are extended to support om tempids
Ok good to know, I see that you got that covered in the middleware.clj files you supply in your talks repo (and probably in many other projects).
anybody seeing non-deterministic behavior around props for componentWillUpdate
and componentDidUpdate
? sometimes the next-props argument has the old props, sometimes it doesn’t
(componentWillUpdate [this next-props _]
(js/console.log "Will” (clojure.data/diff (om/props this) next-props)))