I'm using clojure.spec to validate responses from a particularly poorly written API, and explain-data is seriously my new best friend. 👍

glv: Thanks! That did appear to make things better, but this is still pegging my CPU so I’ll work at it a little more 🙂

Yeah … in my experiments it helped some, but not dramatically.

part of the problem is that json schema is naturally extremely recursive

but the ones that actually exist are wide, not deep

the problem is that that implies statefulness in the recursion, IIUC

I want to recurse a lot high in the tree, less so at the bottom of he tree

Is there a shorthand for saying "no other keys” in a way that’s automatically generator efficient? I realize that these are normally intended to be open for extension, but this is an existing spec, and it is not open for extension

I would expect test/check to peg your CPU, though. For this kind of thing it's definitely CPU-bound. If you're not getting out-of-memory errors anymore, that's an improvement.

You can override generators at paths

Could let you use different gens at different levels

Wow, I've totally missed that. Doc pointer?

Was added recently, not sure there are any docs other than the api

Any place that takes a gen override map can take a vector of keys

Ah, interesting. Will check into that. Thanks!

Although I don't remember now if those are spec keys or path keys or both

Some help you are. ;-)

Yeah

It has to be the path keys

@bsima: You can access the reader literals in aero 0.4.0, but spec'ing after is okay too

Is it possible to coerce the content of an edn file ? My use case: coerce a configuration map (ex. coming from environ where all values are strings to be able to override them from env vars). It seems that edn/read-string does not accept namespaced keywords. Using load-file seem to lead to problems when trying to aot.