if i write params like,

:parameters {:body {:name ::user-spec/name
                                :password string?
                                :client-id ::oauth-spec/client-id

then all the keys will be required

however, if i def a spec for it and use that,

parameters {:body ::oauth-spec/exchange-request}

then the swagger ui will show it like one big hash-map

i need to do

:parameters {:body (s/keys :req-un [...]
                           :opt-un [...])}

but i'd prefer to have my specs defined in one place (not in the routes definition directly)

is there a way to accomplish that?

my current solution is defing it as a map instead of a spec

(def exchange-spec
  {:body (s/merge
           (s/or :code ::exchange-by-code
                 :pass ::exchange-by-auth)
           (s/keys :req-un [::grant-type]
                   :opt-un [::client-id ::client-secret]))})

actually that doesn't work either hmm

or are body params by default shown in a block like that?

@vale swagger-ui shows the body-params as a one json schema by default.

all right then

it was confusing

you can make the parameters optional in the data-spec syntax with ds/opt

I think there is a swgger-ui option to show the body as a html form

yes, set :jsonEditor to true anf you should see the form (https://github.com/swagger-api/swagger-ui/blob/2.x/README.md)

works only with 2.* swagger-ui

e.g. :config {:jsonEditor true} to swagger-ui handler options.

screenshot welcome if that works

(create-swagger-ui-handler {:path "/swagger"
                                  :config {:jsonEditor true}})

yes, it should. Doesn't work?

yeah it doesn't seem to change anything

lemme try again

no luck

:( could you write an issue out of that, I can check when near computer. Could be a regression in the swagger-ui project too.

sure, gonna do that