superstructor 2021-04-14T00:18:59.178100Z

I've also found the domain/ui split useful.

superstructor 2021-04-14T00:23:30.178300Z

Esp for domain data have been looking into datascript, datahike and the like for flat storage and datalog querying of data. So far its obvious that posh/re-posh should be avoided as the query analyzer is significantly slower than the queries themselves (e.g. see Otherwise havn't made many conclusions so far. I'm considering if async cofx/interceptor chains should be supported for datahike-like use-cases but I'm not sure thats even a sane idea yet.

beders 2021-04-14T03:58:48.178800Z

I like the signal graph and would like to keep its properties (i.e. recomputation only when necessary). Having fns that grab data from deep within the app-db run a bit counter to this

beders 2021-04-14T03:59:12.179Z

have tried posh, but found it a bit too much effort

restenb 2021-04-14T08:22:36.181100Z

quick question. re-frame's HTTP client expects :on-success and :on-failure to be defined as events. is there a way to no-op these in the case I want to do nothing with the response?

restenb 2021-04-14T08:23:01.181800Z

that is, a way that doesn't involve just making a :no-op event handler, which of course is trivial enough

p-himik 2021-04-14T08:25:11.181900Z

Just don't specify the keys.

restenb 2021-04-14T08:35:08.182100Z

perhaps, but you get a console error then that annoys me re-frame: no :event handler registered for: :http-no-on-success

p-himik 2021-04-14T08:38:37.182300Z

Ah, huh, yeah. Well, either your own :no-op with explicit keys or your own :http-no-on-success and :http-no-on-failure without the keys.

p-himik 2021-04-14T08:39:41.182500Z

(doseq [id [:http-no-on-success :http-no-on-failure]]
  (rf/reg-event-ctx id (fn [ctx _] ctx)))