@lwhorton I don't think you can spec protocols, the recommendation I got at the time was to create a regular function in front of the protocol function and spec that

https://clojurians-log.clojureverse.org/clojure-spec/2016-06-09.html#inst-2016-06-09T00:06:42.000541Z

yea .. that’s what I’m rolling with. I probably wasn’t clear, but in my question I’m trying to address the issue with trying to test.check multiple “regular functions in front of the protocol function” for each possible argument type

as @seancorfield mentions, they’re open for extension so you can’t cover every base. that being said, i’m only trying to cover my particular bases.

Worth remembering also that you can spec that the value your wrapping fn receives satisfies? the protocol. You’ll need to write a custom generator to generate conforming values for each of the implementations you care about though. You don’t get that for free like you do with multi-spec.

This said if your implementations had a common construction interface… e.g. they all took a string as a single argument to their constructor, you could easily write a dynamic generator by inspecting the protocol i.e. by using (keys (:impls foo.bar/Protocol))

then mapping the implementation classes to constructors/generators

does anybody have any specs around HTML5 filetypes?

I have a fn I'd like to spec but am currently omitting spec'ing one particular argument, which I'm expecting to be an HTML5 File/Blob

@bbrinck hey ben, do I have to do anything special to make expound work in CLJS?

nvm I didn't realize the transition from cljs.spec -> cljs.spec.alpha

had happened

all good now 🙂

@samueldev I’ll add that to the README

A user has also reported a issue on CLJS 1.9.671 (I had been testing on CLJS 1.9.542). Just FYI: https://github.com/bhb/expound/issues/3

@bbrinck using the lib and converted all my spec explains to yours this morning; quite pleased 🙂

its aim seems to be to output developer-friendly error messages; have you considered the use case of going all the way and having it output non-developer-friendly error messages, that can be presented to an end-user? for example if I'm doing some simple validation on a POST route in my API to create an entity, and they omit a required key, an output-string provided along the lines of "Missing required key: _____"

as it stands now, I'm using regular spec explains and iterating over the problems and generating these strings

(with some hard-coded mappings from something like a str? predicate failing --> a string being generated along the lines of "Value provided for key ____ must be a string."

this is something I've considered lib-ifying for my own sake but could instead PR it into expound perhaps, if you see value in it

for a spec that can potentially generate huge values (like giant nested maps with long keywords), what is the most efficient way to get a small values (for playing around with at the repl)

for some reason, my spec errors are printed without newline, which makes them completely unreadable:

:error-while-loading kleinheit.datomic.impl
#error {
 :cause "Call to clojure.core/refer-clojure did not conform to spec:\nIn: [2 1] val: :as fails at: [:args :exclude :op :quoted-spec :spec] predicate: #{:exclude}\nIn: [2 1] va......

any idea what might cause this?

@schmee It looks like you’re printing out the entire error record. Is it possible to just get the :cause and print that?

I hope so 😄

I don’t get why it prints the whole error record in the first place

Sorry, what is “it”?

lein repl 🙂

Ah, I see. Can you perhaps write a wrapper function that calls the function in a try/catch?

I have not tested this, but you could

@schmee Or, after you see an error like that, could you just do something like (println (:cause (ex-data *e))) to print out the cause of the last error?

I suppose so, but I would prefer if I could get the REPL to always do that for me

(just put that on the REPL after the error has been caused)

@schmee I haven’t tried this, but it looks like lein let’s you configure the error handler https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L357-L370. Note that by only printing the cause, you’ll presumably be losing other contextual information about the error, which may or may not be useful.

In any case, this isn’t really related to spec, so you may have more luck tracking down an answer in #leiningen . Good luck!

ahh, now that’s what I’m looking for, thanks! 😄

is there a “recursive” version of describe, that resolves non-fn specs?

not currently

what’s the easiest way to constrain a s/cat into a vector?

(s/and vector? (s/cat ...)) seem to fail to generate data with exercise

here’s how I’m doing it now, just curious if there is a better way:

(spec/def ::pred* (spec/cat :k any? :pred any?))
(spec/def ::pred (spec/with-gen (spec/and vector? ::pred*) #(gen/fmap vec (spec/gen ::pred*))))

@schmee My understanding is that vector sequences is a known problem that isn’t yet solved: https://clojurians.slack.com/archives/C1B1BB2Q3/p14988354

Or, perhaps I should say “regex specs that are also vectors”

I feel like in some platonic sense the regex specs fit seqs much more than vectors but that doesn't mean it wouldn't be terribly useful to have regexes for vectors

probably mostly/entirely for macros?

I’ve also had use cases when using conform/unform on vectors

We have cases where we like the succinctness of using vectors e.g. something like hiccup: [:p {} "hi"]. When we manipulate it, it’s handy to have named parts by using a regex spec, but then we can unform it back to the vector form

Right now we have to unform, then convert the list to a vector

yeah, a catv would be nice

is there a JIRA or something for this?

https://dev.clojure.org/jira/browse/CLJ-2021

cheers 👍

are there/will there be specs for the return values of explain-data?

there’s a JIRA for “specs-for-spec”: https://dev.clojure.org/jira/browse/CLJ-2112

@schmee I was doing exactly that yesterday with clojure.test.check.generators and the gen/vector api.

https://clojure.github.io/test.check/clojure.test.check.generators.html#var-vector

you can define the spec with (s/with-gen (s/cat ...) and hand the with-gen something that always returns a vec