Clojurians Log v2

@fmnoise Yes, that's currently the only way to inject a subscription. The alternative is to actually compute the value, when any inputs to it change (which is what a subscription does reactively), and have the value you need (the value of the subscription) materialized in app-db. Perhaps using the on-change Interceptor on any event handlers which make changes to the inputs.

@mikethompson bit of a random idea related to the whole reg-event-dbfx... the general "composition" idea feels tantilisingly close to allowing multiple handlers on one event

That is to say these are kinda equivilent...

(reg-event-dbfx :event-id interceptors [function1 function2 function3])

and

(reg-event-dbfx :event-id interceptors function1)
(reg-event-dbfx :event-id interceptors function2)
(reg-event-dbfx :event-id interceptors function3)

(ignoring potential issues relating to "re-registering" at dev time - surmountable by registering vars #'function1 or giving each a unique key like add-watch)

Value of this might be separation of concerns. You decorate events with behaviour rather than putting one function in charge of the lot.

Bit left field but thought it was worth sharing.

@olivergeorge Each time I think about multiple handlers, I start to also think about ordering of them. Not long later, I tend to back away slowly. It has always seemed complicated for not a lot of additional value. So, it is probably the lack of a compelling usecase that has stopped me wanting to introduce the complexity.

--------- New re-frame feature incoming. Speak now or forever hold your peace https://github.com/day8/re-frame/issues/639#issuecomment-680500053

Does anyone SSR their re-frame app from aws lambda/nodejs?

Any potential pitfalls? Helpful libraries that take care of lambda handler -> express routing?

Yep makes sense

Just a thought. Not directly reg-event-dbfx related. Data literals as handlers could be a handy shortcut for "effects on event" type scenarios. e.g.

(rf/reg-event-fx ::close-db
  (fn [] {:app.fx/close-database {:resolve [::close-db.success]
                                  :reject  [::close-db.error]}}))

(rf/reg-event-fx ::close-db
  {:app.fx/close-database {:resolve [::close-db.success]
                           :reject  [::close-db.error]}})