This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-12
Channels
- # admin-announcements (1)
- # bangalore-clj (13)
- # beginners (149)
- # boot (123)
- # cider (7)
- # clojure (167)
- # clojure-brasil (3)
- # clojure-greece (1)
- # clojure-korea (2)
- # clojure-new-zealand (2)
- # clojure-russia (70)
- # clojure-sanfrancisco (3)
- # clojure-spec (84)
- # clojure-uk (36)
- # clojurescript (300)
- # code-reviews (242)
- # community-development (34)
- # core-async (4)
- # css (1)
- # cursive (37)
- # datascript (1)
- # datomic (20)
- # defnpodcast (1)
- # dirac (15)
- # events (7)
- # garden (12)
- # hoplon (100)
- # lein-figwheel (11)
- # off-topic (2)
- # om (69)
- # om-next (3)
- # onyx (86)
- # planck (14)
- # proton (4)
- # protorepl (1)
- # quil (2)
- # re-frame (53)
- # rum (3)
- # untangled (1)
- # vim (50)
You seem to contradict yourself @samcf, because in om.next, components don't need any knowledge when dispatching action (in om terms transaction). But if you want re-rednering you need to do the same in om as in redux, subscribe, but think of querying a read
or simply querying
instead of subscribing, though that terminology is used in the re-frame community. The contradiction I see being that you do rely on knowledge of components about what to re-render already in redux.
@hlolli i'm not sure I follow -- in the example I posted, the root component has signaled its interest in :times-greeted
but isn't re-rendered when its child attempts to transact 'greet
> because in om.next, components don't need any knowledge when dispatching action
om.next yells at me when I attempt to transact!
on a component that hasn't implemented om/IQuery -- I guess I'm not sure why it would need to fulfill om/IQuery when its just blindly mutating the state without needing updates