This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-03
Channels
- # aleph (3)
- # beginners (139)
- # boot (3)
- # cider (12)
- # cljs-dev (18)
- # clojure (100)
- # clojure-dev (21)
- # clojure-dusseldorf (5)
- # clojure-germany (1)
- # clojure-italy (35)
- # clojure-nl (26)
- # clojure-spec (4)
- # clojure-uk (60)
- # clojurescript (11)
- # clojutre (4)
- # cursive (21)
- # data-science (21)
- # datomic (47)
- # editors (3)
- # emacs (2)
- # events (4)
- # figwheel (2)
- # fulcro (28)
- # jobs (27)
- # jobs-discuss (21)
- # lein-figwheel (3)
- # midje (2)
- # off-topic (20)
- # om-next (4)
- # onyx (10)
- # overtone (1)
- # pedestal (2)
- # portkey (14)
- # re-frame (71)
- # reagent (44)
- # reitit (11)
- # remote-jobs (1)
- # ring-swagger (4)
- # shadow-cljs (64)
- # spacemacs (11)
- # testing (2)
- # tools-deps (8)
- # vim (8)
@felixb
:keys[:todo/list]
is just a "doc". it's not re-trigged
if you want to re-render do (om/transact this [(my/mutation args) :todo/list])
Thanks @souenzzo but I still don't understand why it doesn't re-trigger. The docs say ":value is an optional hint at keys affected by the mutation; it has no effect on rerendering and should only contain keys valid for :read functions." - why would you want to put a "doc" there that did nothing?
@felixb Did you check out https://awkay.github.io/om-tutorial/#!/om_tutorial.F_Mutation Details on Refreshing Components after Mutation
?
om-next seems pretty much "dormant", might be worth checking out fulcro http://book.fulcrologic.com/ (om-next fork). Pretty active, docs are crazy good.