If I recall, Ring uses empty string "" as empty response. So you could check that the response body value equals to "" if that makes sense.

Or maybe it makes more sense to send an explicit HTTP204 “No Content” response in this case.

E.g. https://github.com/metosin/ring-http-response/blob/master/src/ring/util/http_response.clj#L74-L80

Dunno how much value the validation actually brings here. Unless you’re generating swagger from the routes & schemas.

Thanks! I considered using 204 but I think it may break my tests. I'm generating Swagger!

Hmm swagger docs encourage to leave the content key undefined if empty response is expected https://swagger.io/docs/specification/describing-responses/

Perhaps if you don’t have any schema for the body it will be just fine for Swagger? 🙂

I'll try that out!

Please let me know if that works as expected. 🙂 Just throwing things from the top of my mind, didn’t test

:responses {200 {}} works fine with swagger!

Here’s an example how you can define / override what goes to the swagger spec https://github.com/metosin/reitit/blob/master/examples/ring-malli-swagger/src/example/server.clj#L25-L29

Thanks! I guess that it's not possible to add this "downstream" in the route data? My routes are collected from different namespaces and it would be great if tags could be described locally in each ns rather than at the top level.

I think you can place :swagger {:tags ...} under any routes and reitit will collect & merge them. (again from the top of my head and didn’t try)