@arne-clojurians hi. Yes, that’s looks like bidi 😉 I think you can simplify the app with reitit as you can attach any meta-data to the routes.

In your case, here are some options on modelling with reitit:

(def routes
  [["/" ::login]

   ;; flat routes, custom data
   ["/library"
    {:protected? true
     :name ::library
     :events [[:api/request "get-library"]]}]

   ["/library/:kind"
    {:name ::library-kind
     :parameters {:path {:kind int?}}
     :events [[:api/request "get-library-kind"]]}]]

  ;; nested routes & controllers
  ["/library-nested"
   {:protected? true
    :controllers [load-library-controller]}

   [""
    {:name ::library}]

   ["/:kind"
    {:name ::library-kind
     :parameters {:path {:kind int?}}
     :controllers [load-kind-controller]}]])

e.g. flat-routes (as you have), but just with extra data, which is available on match. or nested routes where you can also nest the loads => going into /library-nested/kikka would invoke :start on both load-library-controller & load-kind-controller

the frontend guides were updated few days ago, hopefully bit better now. there are example project on how to setup reitit too.

oh that looks super nice! thanks for your response, will look into it 🙂

Is there a way to indicate that the same :summary, :handler, etc.. should be used for multiple HTTP methods?

I guess I can just generate them

@robert.mather.rmm yes, you can generate them. You can also put data to top-level route data, which gets merged to all endpoints.

hello everyone, is anybody aware of an example with reitit and buddy-auth? I've just created a boilerplate app with lein new luminus my-api +service +reitit +jetty +postgres +auth-jwe but now Im having trouble to create a 'secure' route