is there a way to get the individual spec keywords mapped to by an s/or call?

looks like describe gets me most of the way if there's nothing better

s/form will be more complete than s/describe

Is there a way to get conformed output to be different for non-regex specs? I have a bunch of strings I need to parse, and I’d like to validate a parsed string against the spec, and returned the parsed values, if they conform

in short, no

you would need a custom spec impl for that currently and I wouldn’t recommend that as the guts are likely to change

in the future, maybe

(s/valid? :fhir-type/PaymentReconciliation
            examples/pay-rec)
false
com.breezeehr.specs.fhir.PaymentReconciliation> 
(s/explain :fhir-type/PaymentReconciliation
            examples/pay-rec)
Success!
nil

@dpsutton I have seen some occasional bugs reported against spec that seem to have that behavior -- I guess you'll need to dig into that :fhir-type/PaymentReconciliation spec and see what it's doing?

It kinda sorted itself out but no idea what the transient state was. Just wondering if it was known bug or if we were way off the beaten trail

Ah, a Heisenspec? 🙂

I'm guessing it's more simple and just something silly we are doing. But you never know