This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-15
Channels
- # beginners (138)
- # bigdata (2)
- # boot (45)
- # cljsrn (29)
- # clojure (108)
- # clojure-austin (1)
- # clojure-gamedev (1)
- # clojure-korea (9)
- # clojure-russia (50)
- # clojure-spec (2)
- # clojure-uk (28)
- # clojurescript (40)
- # component (1)
- # cursive (35)
- # datomic (39)
- # dirac (16)
- # emacs (22)
- # flambo (11)
- # funcool (6)
- # hoplon (74)
- # leiningen (4)
- # off-topic (1)
- # om-next (2)
- # onyx (141)
- # planck (7)
- # proton (10)
- # protorepl (4)
- # re-frame (21)
- # reagent (13)
- # remote-jobs (1)
- # ring (3)
- # specter (9)
- # sql (3)
- # test-check (14)
- # untangled (1)
- # vim (9)
- # yada (16)
@sandqvist: Yeah. I’m using Posh, but I still want the separation of concerns (update fns vs subscriptions) that re-frame provides. It looks like I’m just going to assoc the datascript conn onto the app-db during the (dispatch [:initialize-db datascript-conn])
call. It feels like a hack, but then again maybe re-frame shouldn’t be holding onto it’s own state. This seems to be what Posh is recommending:
https://github.com/mpdairy/posh/wiki/Re-frame-Integration