I don't use Compojure on a regular basis (sometimes with years in between), so I always hit the wiki to find out how it is used. The basics are really intuitive and easy to get up and running. But I always struggle to figure out how the more complex stuff works. Specifically I have two reoccurring issues that I get stuck with every time, where I have to turn to web searches (usually ending up on S

I struggled to setup ring for development and production, as there are so many options.

I tried to compile what I found into two pages https://github.com/laliluna/ring/wiki/Setup-for-development and https://github.com/laliluna/ring/wiki/Setup-for-production

In addition I structured the Home page to make it a bit easier to read.
https://github.com/laliluna/ring/wiki

The examples are more

Looks like it should be "Not all child routes satisfy compojure.api.routes/Routing."

Maybe a fix could use (str ::Routing) or some derivative

-Victor

Swagger feature docstring (and spec?) places tags on route-data root:

https://github.com/metosin/reitit/blob/master/modules/reitit-swagger/src/reitit/swagger.cljc#L55

Examples place tags key under swagger:

https://github.com/metosin/reitit/blob/master/examples/ring-swagger/src/example/server.clj#L30

Both seem to generate proper swagger.json, but first one fails spec validation. Why? Sp

I am using CIDER 0.20.0, cider-nrepl 0.20.0, and nREPL 0.5.3 in my project. Also, I have used :ring :nrepl :start? true option to create a nrepl session when running lein ring server command. However, when I tried to connect to nREPL session via cider-connect, there were bunch of exceptions and I couldn't connect to nREPL session at all. It turned out that add-optional-nrepl-dep functio

As you helped me understand in the issue on ring anti-forgery, a normal punter will try to use wrap-defaults with site-defaults and then add wrap-anti-forgery, not realising that it is redundant.

How could we best add docs to indicate how to handle CSRF / XSRF validation? I guess you're suggesting a complete map of default opt

ring-defaults' wrap-defaults adds the ring.middleware.content-type/wrap-content-type middleware by default (see https://github.com/ring-clojure/ring-defaults/blob/master/src/ring/middleware/defaults.clj#L27 and further occurences of :content-types)
Muuntaja's muuntaja.middleware/wrap-format will silently not do anything when ring's content-type middleware is also present.

Is it possibl

If a regex uses capturing groups, path parameters following the pattern get assigned values from the captured group, not the value from the path.

;; Clout version 2.1.2
(clout/route-matches (clout/route-compile "/:foo/:bar" {:foo #"a(bcd|ef)g"})
(mock/request :get "/abcdg/1"))
=> {:bar "bcd", :foo "abcdg"}

expected:
=> {:bar "1", :foo "abcdg"}

I've found it a bit hard to debug the routing syntax when it fails to pass the valid? pre condition: https://github.com/weavejester/ataraxy/blob/master/src/ataraxy/core.clj#L65-L68