Tommi Reiman

Interceptors should also handle thrown errors, e.g. `:error`.

+ a function to take the spec-modelled data and produces a openapi-spec out of it. should have tests to verify that the generated end results conforms to the Swagger JSON...

mostly done, in `spec-swagger.swagger2.spec`. Should we use vanilla `clojure.spec` instead of `data-specs`?

out of these, I would prefer 3, then 4, both 2 & 1 seem hacks to me. ### 1) partial ```clj (dev-tools/start! {:state-atom re-frame.db/app-db :panels-fn {:permissions {:label "Permissions" :fn (partial...

yes. As long as these are separate libs, would be cool not to need to depend on ring-swagger from spec-side. Lots of deps. ring-swagger 1.0.0 could be a modularized version...

ok, so this could be the plan: 1) copy-paste the validator here to make spec-swagger independent for now. 2) modularize/split ring-swagger into parts when spec-swagger is "done". Parts could be...

Root cause in in the seagger-ui itself. does this work with newer versions of that?

Commented also the issue. Hopefully there will be a quick fix for this.

Hi. Agree on better error messages. For this case: your schema has a `s/Str` as a key, which is not currently allowed. `s/Keyword` should work. Will fix that soon.

the root cause should be fixed in `[metosin/ring-swagger "0.22.2-SNAPSHOT"]`.