@ikitommi presented ongoing work on error messages in reitit at Tampere Clojure Meetup on Tuesday: https://youtu.be/RA2wo2wxfSk

Or do I need to set up an error dispatch like Pedestal?

@grierson it should be {:post {:interceptors [(over-capacity? capacity)]}}

{:post (over-capacity? capacity)} expands to {:post {:handler (over-capacity? capacity)}} and the `:handler is a function of request->response

I’m not 100% if the http-router requires there to be a :handler, it should not.

you can ask the expanded routes with r/routes. e.g.

Simple interceptor example for reference: https://metosin.github.io/reitit/http/interceptors.html

(-> app (reitit.http/get-router) (reitit.core/routes))

Yes, sorry. I was typing the app bit straight into Slack. I've updated the code now.

I’m not 100% sure if the interceptor will catch it’s own errors on :error, but it should.

Right, thats what I was wondering.

When throwing the Exception in the Interceptor should the exception-interceptor pick it up? Then call the :error on the same interceptor that threw the exception?

(require '[reitit.http :as http])
(require '[reitit.interceptor.sieppari :as sieppari])

(def app
  (http/ring-handler
    (http/router
      ["/" {:interceptors [{:enter (fn [ctx] (throw (RuntimeException. "1")))
                            :error (fn [ctx] (-> ctx
                                                 (dissoc :error)
                                                 (assoc :response {:statys 200, :body "fail"})))}]}])
    {:executor sieppari/executor}))

(app {:request-method :get, :uri "/"})
; {:statys 200, :body "fail"}

I seems to work as expected, but will ensure there is a test for that too.

also, the interceptor-part needs A LOT of documentation.

I think I must of needed to dissoc :error

It's working now.

In my error I was just returning a map with just a :response key

oh, yes, the :error is the indicator that it’s still wrong. Not documented properly.

Thank you.

np.