This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-11
Channels
- # admin-announcements (8)
- # announcements (1)
- # boot (343)
- # braid-chat (23)
- # cider (20)
- # clara (5)
- # cljsrn (48)
- # clojars (5)
- # clojure (90)
- # clojure-canada (3)
- # clojure-czech (1)
- # clojure-russia (107)
- # clojure-sg (2)
- # clojurebridge (2)
- # clojured (10)
- # clojurescript (70)
- # community-development (73)
- # cursive (106)
- # datavis (40)
- # datomic (40)
- # docs (4)
- # editors (1)
- # emacs (1)
- # events (4)
- # funcool (2)
- # hoplon (46)
- # jobs (2)
- # ldnclj (11)
- # mount (8)
- # om (214)
- # onyx (12)
- # re-frame (35)
- # reagent (31)
- # spacemacs (12)
- # yada (18)
Good Morning, Onyx team. Happy new year
what's the idiomatic way to do something else, right after transacting to datomic in an output task? (or any other output task), like say you want to transact to datomic, and only after you know that has succeeded, add it to another queue somewhere. lifecycle? output function?
@greywolve, @lucasbradstreet just got married this weekend (congrats, Lucas!), so you’ll have to wait for @michaeldrogalis to rise from his slumber
Morning! Thanks @lowl4tency, you too.
@greywolve: I'd use another lifecycle, placed directly behind the Datomic transaction.
Agreed :)
@lucasbradstreet: congratulations