Tommi Reiman
Tommi Reiman
I think the core change is for the content-negotiation & better json-schema mappings. The rest (security &) are anyway left for client apps / libs to do as there are...
I think we could move the swagger parameter mapping from spec-tools and schema-tools into `reitit-spec` and `reitit-schma` modules. `reitit-malli` already does this: only the malli->JSON Schema mappings are in malli...
Where to find the relevant (swagger2) code with malli: * generate the apidocs: https://github.com/metosin/reitit/blob/master/modules/reitit-malli/src/reitit/coercion/malli.cljc#L140-L165 * swagger parameters: https://github.com/metosin/reitit/blob/master/modules/reitit-malli/src/reitit/coercion/malli.cljc#L82-L103
Helpful errors and Dev experience in general :+1: :+1:
Route data validation is not on by default, here's the guide: https://cljdoc.org/d/metosin/reitit/0.3.9/doc/ring/route-data-validation
One thing that comes to mind is that how should the middleware be configured. In reitit, there are options: 1. **via middleware options** pass the store etc. options for a...
It definetely has, but I was thinking that the endpoint could be made to response with sample data without having any implementation, the conforms to the spec/schema. e.g. a dummy...
Better documentation on this most welcome.
From Slack #sci: > I think there are ... options here. > > first: make all the def defns and split them into smaller parts, e.g. `clojure-set-bindings`, `clojure-walk-bindings` etc. >...