Fork me on GitHub
#re-frame
<
2016-09-13
>
superstructor02:09:45

has anyone tried writing tooling to draw a state diagram from the handler definitions and dispatch calls yet ?

danielcompton04:09:50

some prior art, but not sure if anyone has taken it all the way

nilrecurring05:09:30

@superstructor: are you working on something similar?

superstructor06:09:35

@nilrecurring not yet, thinking about it.

si1411:09:13

just wondering: are there any plans regarding https://github.com/Day8/re-frame/pull/107 ?

lwhorton14:09:11

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 db

lwhorton15:09:14

Or 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]

lwhorton15:09:43

@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

si1415:09:41

@lwhorton true! Somehow I missed that fact

danielcompton23:09:58

@si14 This is on my mind quite a bit, I know Mike’s thinking about it too, but no immediate plans