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 that I
read too much into your post.
But I'm curious about bigger-picture issues: why wouldn't you include
something like swagger as part of your public API?
(Don't get me wrong: I can think of 4 different reasons off the top of my
head. I'm just curious why you don't want to).
On Wednesday, February 20, 2019 at 11:24:01 AM UTC-6, Brjánn Ljótsson wrote:
>
> 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 included in my production build. What
> is the best way to disable swagger in production?
>
> Best,
> Brjánn Ljótsson
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
