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

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

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

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

I needed to add

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

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

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?