@henrik. Looks like you've quoted common-interceptors in the second case.

Oh, right, so now I’ve learned about backtick.

Why are the routes quoted to begin with? I’m working from the leiningen template. https://github.com/pedestal/pedestal/tree/master/service-template/src/leiningen/new/pedestal_service

@henrik, I’ve not looked at the impl for map-based routes so I can’t comment on them. My preference is the tabular routing syntax. I find them much easier to grok.

Fair enough. In the case of tabular routes, the back tick sits on the routing function itself. In the “hello world” guide, there’s no back tick:

(def routes
  (route/expand-routes                                   
   #{["/greet" :get respond-hello :route-name :greet]}))

;; Tabular routes
(def routes #{["/" :get (conj common-interceptors `home-page)]
              ["/about" :get (conj common-interceptors `about-page)]})

(-> service/service ;; start with production configuration
      (merge {…
              ::server/routes #(route/expand-routes (deref #'service/routes))
              …}})

The backticks in service.clj lead to fully qualified symbols that get resolved here: https://github.com/pedestal/pedestal/blob/master/interceptor/src/io/pedestal/interceptor.clj#L49

The deref allows routes to be reloaded without having to restart the server

you can make changes and load the service ns again