hmm, master...

maybe into sql branch first

conflict in project.clj but not too bad

this ::mapping spec is monstruous

😄

could it be expressed without a spec at all?

its main problem to me is that it’s doing too many things at once

as in something could be deferred to be done later or too much code inline?

given a spec, we want: • a schema • converting to a row • the serializer part of the encoder • converting from a row • the deserializer part of the encoder

given a schema, we want a spec (and from this spec gets the conversion fns)

::mapping tries to do everything at once (modulo encoders)

hmm, master...

is ::mapping currently to much to be fed into master branch?

just had to try out the “master” summon again 🙂

yes too hacky even by powderkeg standards

😄