@ikitommi just confirming that with the changes, a custom :string/decode on a schema entry will still fully overwrite the default mt/string-transformer for the type, yes? I think that escape hatch is quite useful.

@rschmukler yes, will override, no changes there

Wonderful! Reading through the code but it looks great so far

just chains all the different names.

Hmmmm - do we even need transformer-chain protocol method?

Is it just for introspection?

I guess we're using it to assemble the interceptor chain

oh, good point.

But I think we could move all of that into the transformer function and then simplify Transformer to a single value-transformer method, which could be nice

@ikitommi do you have any thoughts on https://github.com/metosin/malli/pull/132

It ended up being critical for my application (the ability to encode the renaming of keys for future transformers) but I'm open to alternative approaches if you've got other ideas you want me to explore

Part of me thinks using metadata is odd - part of me thinks that this is the perfect use case for it

ie. it is metadata about how the new value was created... so maybe it makes sense?

One thing we may have to do though, if we end up sticking with that API, is merge the metadata about transformers as we compose them

Also, random aside, but malli is Finish, correct?