I don't know - try it? You can specify a generator too

yep, generating works fine with :kind sequential?

fyi, snippets slow down slack a lot. Maybe we should default to creating posts instead of snippets.

I keep having to with-gen or overspecify my generator in clojurescript as generation just takes too long and eventually times out.

Specifically coll? as a :args always causes me to eventually time out

Anything clever to fix this?

Oh, I mean when using clojure.spec.test/check.

> (defn fx [coll] coll)
> (s/fdef fx :args (s/cat :coll coll?))
> (stest/summarize-results (stest/check `fx))

As an example of timing out in cljs.

Have you tried using the :gen-max option?

nope

For spec'ing collections that is

yeah, I saw one example of that in the spec getting started guide, forgot about it.

You could use (s/coll-of any? :gen-max 3)

i’m looking at doing form validation using spec. any thoughts on mapping from an explain to a slightly more human readable messages to put under fields? can’t find anything to put metadata on

maybe just a map from spec keys to messages would do

hmm, looks like i’d need to key off the pred symbol actually

user=> (s/explain-data (s/keys :req [::foo]) {::foo ""})
#:clojure.spec{:problems ({:path [:user/foo], :pred not-empty, :val "", :via [:user/foo], :in [:user/foo]})}

@alexmiller Thank you for your help. I played around with it since then. Actually, the real issue was that I was including a spec in the :ret part of my s/fdef. This causes the value in :ret in the :fn part of the same s/fdef to be the spec-conformed-return version of the :ret, not the function-value-return version of the return. Kept causing failures that I just couldn’t understand. 🙂

tldr; If your spec does not conform to the identity of the value passed to it, you should think about what you are doing when using it in s/fdef’s :ret

hrm, wrapping it in s/and allows you to retrieve the “ground” spec:

cljs.user=> (cljs.spec/explain-data (cljs.spec/keys :req [::foo]) {::foo ""})
{:cljs.spec/problems {[:cljs.user/foo] {:pred not-empty?, :val "", :via [:cljs.user/foo], :in [:cljs.user/foo]}}}
cljs.user=> (cljs.spec/def ::foo (cljs.spec/and ::not-empty))
:cljs.user/foo
cljs.user=> (cljs.spec/explain-data (cljs.spec/keys :req [::foo]) {::foo ""})
{:cljs.spec/problems {[:cljs.user/foo] {:pred not-empty?, :val "", :via [:cljs.user/foo :cljs.user/not-empty], :in [:cljs.user/foo]}}}

(difference is in :via values)

@spieden Thanks you for letting me know, I did reach that solution as well. It all makes pretty good sense, it just caught me by surprise that :ret also effected the :ret in :fn.