Pauli Jaakkola

Transformers could have some more documentation, especially around implementing custom ones.

Well the `path` vector would not come for free, at least with dynamic keys (e.g. `:map-of`). The documentation needs to be improved in any case; the nonvalidating best-effort model is...

Easy with `validate`, but challenging if we wan't to use `validator` instead. On Cljs even having the `assert` macro create the validator is not possible.

Apparently Typed Clojure can automagically infer Specs.

This might be hard (or not). IMHO we should not make any guarantees about how (partially) invalid input is decoded. (Ceterum censeo, it should produce an error but that is...

We would have to keep the longest partial decoding around and then return that if the full sequence cannot be decoded. Maybe not super difficult but definitely additional complexity and...

Ah I might have it the wrong way around, in that case you would first decode and then validate... still I think the coercer would be more optimal. Either way...

> If you haven't required `sieppari.async.manifold`, Sieppari will quietly use the `future`-using AsyncContext implementation for `clojure.lang.IDeref` (which Deferred is an instance of). This is terrible.

It would be more symmetric and principled to have both `enter-fn->interceptor` and `leave-fn->interceptor` (or perhaps `preprocessor` and `postprocessor`) and having the handler be just a function. It would be more...

The handler could also be a function `ctx -> ctx`... but really the handler should work like in prior art (Pedestal, re-frame). The request-response convention is nice, but not the...