This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-18
Channels
- # beginners (15)
- # boot (23)
- # cider (8)
- # clara (29)
- # cljs-dev (86)
- # cljsrn (36)
- # clojars (9)
- # clojure (211)
- # clojure-dusseldorf (5)
- # clojure-italy (21)
- # clojure-sg (2)
- # clojure-spec (4)
- # clojure-uk (12)
- # clojurescript (204)
- # cursive (5)
- # data-science (12)
- # datomic (15)
- # dirac (99)
- # emacs (1)
- # events (2)
- # figwheel (1)
- # fulcro (9)
- # graphql (27)
- # hoplon (50)
- # instaparse (9)
- # juxt (61)
- # keechma (6)
- # leiningen (1)
- # luminus (4)
- # lumo (24)
- # off-topic (24)
- # om (16)
- # onyx (17)
- # parinfer (35)
- # pedestal (3)
- # planck (12)
- # protorepl (8)
- # re-frame (15)
- # reagent (22)
- # ring (1)
- # rum (1)
- # spacemacs (3)
- # uncomplicate (4)
- # vim (5)
- # yada (1)
events don’t affect components – they can affect the app-state, which in turn affects components
@joelsanchez The question you ask is puzzling. In re-frame, components don't communicate. In OM.orig, core.async
is often used as an event bus for Components, but that's not done in re-frame. There's a very different notion of "events".
To build up your re-frame muscles, I'd suggest you chip away at the docs, and look at the examples.
OM.orig and re-frame are very different in approach.
did re-frame suddenly change where ^{:key i} [:li ...] become deprecated and I have to use [:li {:key i} ... ] }
Sounds like a question for Reagent (instead of re-frame). But I'm not aware of any changes.
Guys, any nested value in app-db isn’t writeable ? i.e; (app-db {:a {:b 1}}) (subscribe [:a :b]) ;; (-> db :a :b) so Can not I write this returned value ?
thank you both for your replies
> what I do typically is give each instance of a component some sort of identifier
> pass that to the event dispatch, use it in the app-state and subscriptions
makes sense to me, I just remembered that the re-frame-datatable
component takes an identifier argument, which it uses for identifying that instance's state in the app db, and then you need to use that in your dispatches, so I will follow that
@scknkkrer you can't "write" to a subscription, they are read only