ring-swagger

ring-swagger & compojure-api
ikitommi 2018-02-16T06:07:18.000121Z

@nickmbailey I think context within a context is the way to do that today.

ikitommi 2018-02-16T06:12:34.000083Z

@mgrbyte describe doesn’t work, I should. I believe the :description field of spec-tools Specs should populate that correctly.

1👍
ikitommi 2018-02-16T06:13:41.000099Z

e.g. (st/spec {:spec int? :description "it's an int"}). That could be used to make the describe work with specs too.

slipset 2018-02-16T13:34:10.000253Z

seems like spec-tools and eastwood are not the best friends:

slipset 2018-02-16T13:34:13.000459Z

I needed to add

slipset 2018-02-16T13:34:16.000180Z

(disable-warning
 {:linter :constant-test
  :if-inside-macroexpansion-of #{'spec-tools.core/spec}
  :within-depth 7
  :reason "reasons"})

slipset 2018-02-16T13:35:05.000248Z

for this line (spec-tools/spec (s/and string? object-id?) {:type :object-id})

2018-02-16T20:10:08.000317Z

Hi all, we recently tried to split our swagger UI into two separate UIs on the same server, one for internal endpoints and one for external endpoints. Putting both sets of defapi routes in the same app seems to be blowing up, though (seems to try to read InputStreams in the body twice). Should we be able to have 2 distinct defapi-based route sets in the same app?