Clojurians Log v2

Hello! Its time to add my question too, Can someone explain me how the compiled middlewares (:compile) work? For example, this web-app example https://github.com/PrestanceDesign/usermanager-reitit-integrant-example defines a middleware-db this way:

(def middleware-db
  {:name ::db
   :compile (fn [{:keys [db]} _]
              (fn [handler]
                (fn [req]
                  (handler (assoc req :db db)))))})

here’s the guide: https://cljdoc.org/d/metosin/reitit/0.5.12/doc/ring/compiling-middleware

• 1st arg: the full route data • 2nd arg: router options

hope this helps

nice! Thanks 🙂

In bidi you can define your route and handler separately and then have them mapped through the bidi/make-handler function, for example:

(def route 
 [""
   [["/" :index]
    ["/ping" :ping])

(def handlers
 {:index ...
  :ping ...})

(bidi/make-handler route handlers)

(def routes
  [["/" {:get {:handler ...}}]
   ["/ping" {:get {:handler ...}}]])

Hey team, a bit of a noob question. I am writing my own custom exception / logging middleware. I put them at the end of reitit/router, etc A: wrap at end

(-> (ring/ring-handler (ring/router ...)
    wrap-logging
    wrap-uncaught-exception)

(defn wrap-logging [handler]
  (fn [req] ...))

(defn api-routes []
  ["/api"
   {:middleware [;; uncaught exceptions
                 middleware/wrap-uncaught-exception
                 ;; logging
                 middleware/wrap-logging
                 ;; query-params & form-params

There is the Expand protocol you can override, see https://cljdoc.org/d/metosin/reitit/0.5.12/doc/basics/route-data#customizing-expansion

Linked from there: https://cljdoc.org/d/metosin/reitit/0.5.12/doc/advanced/shared-routes#using-custom-expander

In the first A, the logging is applied before the router is invoked. In ring, the middleware chain in run in reverse order. Inside reitit router, mw is run in reverse-reverse order, e.g. in "right" order.

Thanks for jumping in @ikitommi Would you mind expanding a bit deeper, on how A is being applied before the router is invoked? If it’s

(-> (ring/ring-handler (ring/router ...)
    wrap-logging
    wrap-uncaught-exception)