@rschmukler been using that with schema for 5+ years, no complaints. Cursive does static analysis for that + you can omit the type hints if you don't know/want to define those, e.g

(m/defn plus
  [x :- int?, y] 
  (+ x y))

will check the interceptor PR as soon as have extra time.

the chaining of encoders & decoders with mt/transformer, I think it's a good idea.

https://github.com/danielcompton/defn-spec

there is also: https://github.com/fulcrologic/guardrails/

and https://github.com/jeaye/orchestra/blob/master/README.md#defn-spec

Is there something missing from the original plumatic schema syntax?

@ikitommi I’ve got a proof of concept. I’ve separated the parsing from the code generation (the generation just takes a map). This will allow different styles to work.

Regarding the composition of interceptors, if you don’t mind, I may do it as a separate PR to keep thins more focused.