This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-28
Channels
- # announcements (2)
- # beginners (19)
- # calva (8)
- # cider (5)
- # cljsrn (13)
- # clojure (35)
- # clojure-conj (3)
- # clojure-spain (1)
- # clojure-uk (2)
- # clojurescript (4)
- # clojutre (4)
- # cursive (13)
- # data-science (2)
- # datascript (1)
- # datomic (5)
- # duct (4)
- # fulcro (76)
- # funcool (5)
- # jobs (5)
- # off-topic (10)
- # remote-jobs (7)
- # rewrite-clj (8)
- # spacemacs (3)
- # sql (2)
- # xtdb (25)
:xyz.handler/somehandler
{:db #ig/ref :xyz.database/master
:logger #ig/ref :duct/logger
:cache #ig/ref :xyz.cache/history}
Ok I think I'm starting to get it. And so some handler would be defined as a fn
in it's init-key
implementation? And every function that uses logging would be defined this way instead of defn, and called like
((xyz.handler/some-handler system) x y)
Like a handler example feels somewhat natural as a dependency. But what if I have a function which takes some data from an external API, saves it to a database, does some logging and returns the data. Should this function be defined with init-key and then called by looking up the function in the system map?