@zhoumin79 pedestal requires it’s own Router impl, it doesn’t understand the reitit Router. For this, there is some glue code to swap the routing intereceptor, see https://github.com/metosin/reitit/blob/master/examples/pedestal-swagger/src/example/server.clj#L118-L135

new content-negotiaion docs by @iagwanderson! https://metosin.github.io/reitit/ring/content_negotiation.html

(defmethod ig/init-key :duct.server/pedestal
  [_ {:keys [base-service
             service
             dev?]}]
  (let [config (duct/merge-configs
                base-service
                service)

        {router ::http/router
         port   ::http/port
         host   ::http/host} config]

    (println (str "\nCreating your " (when dev? "[DEV] ")
                  "server http://" (or host "localhost") ":" port))
    (cond-> config
      true (dissoc ::http/router)
      true http/default-interceptors
      true (pedestal/replace-last-interceptor
            (pedestal/routing-interceptor router))
      dev? http/dev-interceptors
      true http/create-server
      true http/start)))

This is my code. Something wrong?

Sorry to waste your time. It’s my bad

@ikitommi I misspelled a config letter.

Reitit is an awesome library.👍

Hi quick question, running reitit with pedestal, is there a suggested resolution for this? Perhaps a wrapper or something? > There is no common interceptor spec for Clojure and all default reitit interceptors (coercion, exceptions etc.) use the Sieppari interceptor model. It is mostly compatible with the Pedestal Interceptor model, only exception being that the `:error` handlers take just 1 arity (`context`) compared to Pedestal’s 2-arity (`context` and `exception`). > > Currently, out of the reitit default interceptors, there is only the `reitit.http.interceptors.exception/exception-interceptor` which has the `:error` defined.

Is there an example of using clojure spec to validate a POST body?

@eoliphant the reitit-pedestal module should take care of that.

^:--- the latest swagger-ui (3.*) looks like that. I guess we could upgrade to that.

seems to work ok. not a fan of the new ui, but it’s kinda de facto nowadays.

pushed out 0.4.2, which has direct dependency to jackson-core, to fix this sadly-way-too-common maven issue: https://clojureverse.org/t/depending-on-the-right-versions-of-jackson-libraries/5111