Re: Disable swagger.ui in production

2019-02-22 Thread James Gatannah
I'm going to buck a trend here. Why do you want to do this? (That's rhetorical. Don't feel like you need to answer). One of the fundamental principles behind REST is that it is discoverable. Maybe even that it's explorable. Maybe you aren't building a REST end-point. It's totally possible

Re: Disable swagger.ui in production

2019-02-21 Thread brjann
Hi, Thank you for the suggestion! I also got a backchannel reply that one could simply put the swagger map in a (when dev-mode? {:swagger {...}}) form. For some reason I though that wouldn't be possible because api is a macro but that actually works fine. Thanks, Brjánn On Thu, 21 Feb 2019 at

Re: Disable swagger.ui in production

2019-02-20 Thread Matching Socks
Would it be fair to paraphrase the question as, how to pass a different data structure to compojure's api function depending on whether the program is running in the development environment or "in production"? One very general technique is to wield the classpath to advantage. Suppose for

Disable swagger.ui in production

2019-02-20 Thread brjann
Hi, I'm trying out compojure-api and have included swagger.ui in my api: (api {:swagger {:ui "/swagger-ui" :spec "/swagger.json" :data {:info {:version "1.0.0" :title "Title" ...) However, I don't want swagger to be