want to share with you i'm working on

@knaman you have to create a subscription, which filters the alerts and then register to that one.

@danielgrosse filter by what? alerts is simply a list of alert items

I try to get my head around the reg-event-fx function. So the cofx argument is the db, which is returned by the dispatch function?

@knaman

(reg-sub
 :newest-alerts
 :<- [:alerts]
(fn [alerts _]
(filter #(> date %) alerts))

You subscripe to this subscription in a new one, and then modify the data to the needed form. Then you can subscripe to it in your edit function

@danielgrosse ok, but the edit is like a modal box, so that function will be called even when a new alert is added

So the edit box opens if a alert occurs?

@danielgrosse no, there is an edit button which opens the relevant edit box

@danielgrosse ok, seems like if dont access @alerts in side fn and instead use in let , it doesnt gets called

What’s a good strategy for writing asynchronous subscription handlers? i.e, their computation function has an async call for some reason or another (io and such)

@tomerweller set a complete flag in the app db when async fn has completed?

@michael.heuberger you mean dispatching an event and subscribing for the relevant path in the db?