This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-30
Channels
- # announcements (14)
- # aws (2)
- # beginners (167)
- # calva (25)
- # cider (124)
- # cljs-dev (2)
- # cljsrn (7)
- # clojars (2)
- # clojure (113)
- # clojure-europe (2)
- # clojure-italy (6)
- # clojure-spec (30)
- # clojure-uk (90)
- # clojurescript (20)
- # code-reviews (16)
- # cursive (28)
- # data-science (2)
- # datomic (89)
- # duct (97)
- # emacs (4)
- # figwheel-main (12)
- # fulcro (37)
- # graphql (3)
- # java (3)
- # jobs (2)
- # juxt (3)
- # kaocha (37)
- # leiningen (2)
- # luminus (2)
- # off-topic (30)
- # onyx (2)
- # pathom (3)
- # qlkit (1)
- # re-frame (7)
- # reagent (2)
- # reitit (62)
- # remote-jobs (9)
- # shadow-cljs (26)
- # tools-deps (19)
- # vim (1)
- # yada (8)
I'm working to update the io.aviso/pretty library/plugin to work with more recent Leiningen, where implicit middleware and hooks are deprecated. It seems like I need to update my documentation to say "add io.aviso/pretty to :plugins, but also add pretty.plugin/inject-pretty to :middleware". Is that correct, or is there a different mechanism to allow plugins to add middleware. I also have a hook, but it exists just to invoke io.aviso.repl/install-pretty-exceptions (which overrides some functions in clojure.main and clojure.repl). I could move that to the middleware function, but I really prefer that to be executed as early as possible.