I have a problem with not-found route using compojure-api and middleware to wrap authentication. The authentication wrapper “eats” all requests and the not-found route is never matched.

(require '[compojure.api.sweet :as api])

(def handler
  (api/routes
    (api/middleware [auth/wrap-api-authentication]
                    protected-api-routes)
    (route/not-found "Not Found")))

@mhautala wrap-middleware which workslike wrap-routes is available in 2.0 alpha

ok, good to know, so this is a know thing with the middleware function?

yes

Ok, now I noticed that is exactly what it says in the middleware functions documentation

Note that middlewares will be executed even if routes in body
do not match the request uri. Be careful with middlewares that
have side-effects.

@mhautala good solution is to apply authentication for a explicit context. e.g.

(context "/admin-routes" []
  :middleware [auth-wrap-api-authentication]
  ...)

(also, there will be more tools to compose things with 2.0.0.)

Ok that’s a good solution, I found already that approach for endpoint level but at context or api-level you can avoid repeating code

I’m getting a persistent eastwood warn with compojure-api

(ns test-eastwood.core
  (:require [compojure.api.sweet :refer :all]
            [schema.core :as schema]))

(def v1-routes
  (routes
    (POST "/foo" []
          :return {:bar schema/Int}
          {:status 200 :body {:bar 35}})))

gives me

== Linting test-eastwood.core ==
Entering directory `/Users/michael.blume/workspace/test-eastwood'
src/test_eastwood/core.clj:1:1: suspicious-expression: merge called with 1 args.  (merge map) always returns map.  Perhaps there are misplaced parentheses?

both with 1.1.10 and 2.0.0-alpha1

https://github.com/MichaelBlume/eastwood-test if that’s helpful