This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-19
Channels
- # beginners (37)
- # boot (96)
- # cider (23)
- # clara (2)
- # cljs-dev (40)
- # clojars (1)
- # clojure (149)
- # clojure-conj (1)
- # clojure-dev (2)
- # clojure-dusseldorf (5)
- # clojure-france (82)
- # clojure-italy (1)
- # clojure-nlp (1)
- # clojure-russia (13)
- # clojure-spec (24)
- # clojure-uk (62)
- # clojurescript (131)
- # core-async (13)
- # core-logic (7)
- # data-science (1)
- # datomic (10)
- # defnpodcast (3)
- # docker (4)
- # emacs (3)
- # events (4)
- # hoplon (68)
- # klipse (4)
- # leiningen (1)
- # off-topic (5)
- # om (140)
- # onyx (16)
- # pedestal (24)
- # planck (10)
- # proton (2)
- # re-frame (9)
- # reagent (4)
- # remote-jobs (1)
- # ring-swagger (16)
- # untangled (5)
- # vim (8)
- # yada (30)
More fx handlers released, this time “document” related fx/cofx which includes :document/render
to render the root reagent component to the DOM as a side effect: https://github.com/SMX-LTD/re-frame-document-fx
"direct testing": I am not supposed to call the handler directly (because of interceptors), right? And it seems pointless to register. What's the proper way to call it and get the db back?
@deas there’s https://github.com/Day8/re-frame-test in the oven, might be interesting too
this illustrates its usage https://github.com/Day8/re-frame/pull/193
to test the events interceptors and registering, seems like the best way
@rafaelzlisboa Thanks! Will give it a test drive. Will have my food raw in case it does not work for me. 😉