weird, I can't reproduce it in the repl

it's definitely happening in the call to conform though

upgrading from alpha14 to 15 made it go away

What’s the easiest way to make a spec that matches {:a 1 :b 1}, {:a 1}, and {:b 1}, but not {}?

(s/keys :req-un [(or ::a ::b)])

is that regular or or spec/or?

it's s/keys syntax that expands to clojure.core/or

ok, I got it. Thanks!

Is there a way to provide more detailed explain output for a custom conformer? In alpha15 I get a message like: val: "k" fails predicate: (conformer conform-int). I see I can supply an optional "unform", but no arity to supply an "explain"...

is there a way to turn off fdef validation for defn temporarily in -alpha14? I'm seeing a failure in a third party lib that works in another project.clj so I think I'm having classpath issues and I need to load the namespace so I can interogate some objects via the classloader

@manderson you can implement the Spec protocol to provide a custom explainer

word on the street is that the protocol may be changed in the long run

but for now it works fine

if you look at the Spec implementations included in the lib (that are used for keys and tuples, etc) you can get an idea of what kind of output they return

if errors, return a list of errors (like what you get from explain-data), otherwise return empty list/nothing

that example assumes you don't want to do any special conformation

Gotcha, thanks @hospadar. Figured that might be the only way, but was hoping for a "published" approach instead of looking behind the curtain. I'll give that a try.

yeah I feel that

@bja you can s/def your own spec over the top of the standard one

@alexmiller thanks. that's what I eventually settled on

found out that I had a conflict with an older version of potemkin generating non-conforming functions.