This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-13
Channels
- # aws-lambda (21)
- # beginners (8)
- # boot (67)
- # braveandtrue (2)
- # cider (12)
- # cljs-dev (38)
- # cljsjs (87)
- # cljsrn (11)
- # clojure (307)
- # clojure-austin (29)
- # clojure-finland (1)
- # clojure-italy (9)
- # clojure-russia (19)
- # clojure-spec (71)
- # clojure-uk (33)
- # clojurescript (109)
- # clojutre (1)
- # core-async (2)
- # cursive (24)
- # datomic (11)
- # devops (5)
- # ethereum (5)
- # figwheel (2)
- # hoplon (25)
- # ipfs (1)
- # jobs (1)
- # luminus (17)
- # off-topic (2)
- # om (38)
- # om-next (3)
- # onyx (166)
- # other-lisps (1)
- # proton (5)
- # re-frame (15)
- # reagent (45)
- # ring (2)
- # spacemacs (6)
- # specter (12)
- # untangled (58)
- # yada (23)
has anyone tried writing tooling to draw a state diagram from the handler definitions and dispatch calls yet ?
some prior art, but not sure if anyone has taken it all the way
thanks @danielcompton 🙂
@superstructor: are you working on something similar?
@nilrecurring not yet, thinking about it.
just wondering: are there any plans regarding https://github.com/Day8/re-frame/pull/107 ?
Heya guys, is there a way to get the full db
value in reg-sub
using the sugar syntax?
(reframe/reg-sub
:user-settings/state
:<- [:secure/user]
(fn [user db?]
{:state (db>/get-state db)
:user user}))
In something like this the db?
is actually the subscription vector [:user-settings/state]
… not the dbOr would I have to define a subscription somewhere else that’s just the raw db, so my reg-sub would look like
:<- [:db]
:<- [:secure/user]
@si14 I’m not sure on the details of that issue, but I do know that as of re-frame .6ish the event loop doesn’t use core.async any more, which resolved a couple odd browser interaction problems
here it is: https://github.com/Day8/re-frame/blob/19d0fd4021fd22bc8ca9e579d897b8ebf4f6fd6e/CHANGES.md#050--2015-11-5
@si14 This is on my mind quite a bit, I know Mike’s thinking about it too, but no immediate plans