given a spec (obtained from ex-data of an exception thrown by inspect, i.e the :cljs.spec.alpha/spec), how can one obtain the key of that spec in the registry?

I want to go from spec -> the name of the fdef’ed function that failed

My current solution is to parse it out of the exception message, which contains “Call to #‘name-of-var did not conform to spec…“. It would be nice if instrument included the key in the ex-data, but I might be misunderstanding something here.

@odinodin can you give please show the data you are trying to go from -> to?

I think you might want to use (s/form) or (s/get-spec), but I'm not sure yet what you are trying to get

@wilkerlucio it is a spec record object, as provided by the exception thrown by instrument when a fdef’ed function is called with non-conforming input.

it is the spec object that (s/get-spec 'the-fdefed-var) would return as far as I can tell

that's a long chain, hehe, I'm not sure what kind of data you are looking at, can you paste what your (ex-data) result looks like?

This is what (ex-data) returns:

{:cljs.spec.alpha/problems ({:some-description-of-the-problem "..."})
 :cljs.spec.alpha/spec #object[cljs.spec.alpha.t_cljs$spec$alpha56508],
 :cljs.spec.alpha/value ({:foo "bar"}),
 :cljs.spec.alpha/args ({:foo "bar"})
 :cljs.spec.alpha/failure :instrument}

I want to know what the :cljs.spec.alpha/spec object is referring to

or it would probably be more correct to say, what key points to this spec in the registry

@odinodin gotcha, you can try calling (s/form) and (s/get-spec) on it, but I'm not sure if will work

I’ll try that

thanks

@wilkerlucio (s/form) only returns the spec as defined on the (s/fdef) var. I’ll just parse the var out from the error message instead. Anyway, thanks for your suggestions 🙂

no problem, I'm glad you can at least work around it, maybe other people will have a better solution 😉

@odinodin there is a ticket filed for this at https://dev.clojure.org/jira/browse/CLJ-2166 - patches welcome

I just haven’t had time to look at it yet

@alexmiller nice! Just what I was looking for :)

hey all

does anyone know of a library to convert clojure.spec problem explanations to more human-readable output?

https://github.com/bhauman/strictly-specking seems to have some work in this direction, but I don’t think it’s a drop-in solution right now

I’m also working on something now, but it’s early days and not yet ready for release

(inspired by the work in strictly-specking and elm errors)

I’m a bit confused by the value of “in” when using “map-of” https://gist.github.com/bhb/6f06dd07bcf5b275a7d4faf3167bfc85

I searched JIRA but could not find an issue, so it may be a misunderstanding on my part

@samueldev ^-- (sorry, forgot to mention you, see my comment above)

@samueldev I think @ericnormand is also maybe working on something for more human-readable error messages?

thanks @bbrinck ! I'll do some digging with @ericnormand's work and bruces!

I think also the above odinodin is working on something for re-frame