This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-11
Channels
- # adventofcode (7)
- # aws-lambda (1)
- # beginners (161)
- # cider (19)
- # cljsjs (5)
- # cljsrn (30)
- # clojure (80)
- # clojure-korea (2)
- # clojure-new-zealand (8)
- # clojure-russia (73)
- # clojure-sanfrancisco (1)
- # clojure-spec (14)
- # clojure-uk (12)
- # clojurescript (84)
- # cursive (7)
- # defnpodcast (8)
- # dirac (16)
- # events (2)
- # garden (7)
- # hoplon (178)
- # off-topic (2)
- # om (58)
- # om-next (2)
- # onyx (21)
- # pedestal (1)
- # planck (15)
- # protorepl (32)
- # re-frame (31)
- # untangled (1)
- # yada (5)
I'm just jumping into om.next after having written a ton of react/redux -- I'm trying to figure out which patterns still apply and where my thinking might need to change. In Redux, a component can dispatch an action without needing any knowledge of the components who might care about the mutation, and those components who have subscribed to Redux will be re-rendered. This does not seem to be the case in my example app https://gist.github.com/samcf/60908fd94b39089be05a880cec96cac0 where (om.next/transact! this '[(greet)])
is triggered but the parent does not get re-rendered. Am I doing something wrong? Thanks for your time, love CLJS so far
My feeling is that https://github.com/omcljs/om/wiki/Om-Next-FAQ#why-is-my-component-not-rerendered-after-transact has something to say about this but not sure I fully grokked it