shipped both [metosin/compojure-api "1.1.11"] & [metosin/compojure-api "2.0.0-alpha6"], with the s/Num coercion, updated deps & spec coercion does s/unform too.

Is it possible to change the Swagger basePath at runtime? I am able to define it in the api declaration (def myapi (api {:swagger {:data {:basePath "/xxx"}}} …), but I wonder if I can change it somehow. Changing myapi to a defn is not an option.

@psalaberria002 yes you can override everything at runtime.

via middleware?

do you use 1.* or 2.* version?

compojure-api “1.1.10”

ok, there is ring.swagger.middleware/wrap-swagger-data which can be used to inject swagger data in.

nice!

the api puts the whole (statically defined) swagger-data into request under a special key, the swagger-endpoints read that + direct options and merge them together.

hello everyone i have some doubts on how to generate proper documentation using spec this spec

(s/def ::non-empty-string (s/and st/string? #(> (count %) 0)))

{ "holdersName": {} }

@plins s/and is fixed in the latest spec-tools snapshot, see https://github.com/metosin/spec-tools/blob/master/CHANGELOG.md#031-snapshot

... but you can force a type with (st/spec #(> % 10) {:type :string}).

looks like 0.3.1 isnt on clojars, lein cant resolve it as a dependency

but hey, thx for the fast response 🙂

yeah, snapshot only. I'll push it out when at laptop. The automatic type resolution rules are here: https://github.com/metosin/spec-tools/blob/master/src/spec_tools/type.cljc