@mrchance check out https://github.com/immoh/swagger-spec

@ikitommi Thanks, but I don't want to generate swagger, but the data consumed by the interfaces specified in a swagger file. It doesn't look like that is possible with swagger-spec?

oh, the endpoint data. With vanilla swagger spec, there needs to be a JSON-Schema -> Spec converter, I don’t know if such exists yet. But if you describe your endpoints with spec, you get the data generation for free.

Yes, already doing that, unfortunately some of the other services in my project aren't written in Clojure. If one were to write such a converter, how would one go about it? I invested an afternoon because I didn't really find anything too, but it seemed really hard and messy to generate specs at runtime, due to its reliance on global mutable state 😞

Maybe <gasp> generate code </gasp> ?

@ikitommi I saw that you had schema like maps in your spec tools, which could be handled like normal data. Would that be an option for this case?

Some more “functional specs” might be coming to core, but while waiting, yes, there are some rogue versions at https://github.com/metosin/spec-tools/blob/master/src/spec_tools/data_spec.cljc#L8-L10 and the data-specs on top of those.

most/all of the core specs have functional versions already in the core, but currently not documented and the apis are bit hairy. Maybe those will be polished and published as part of the public api? The forms need to be created manually but for most core predicates, it’s easy to resolve those (and spec-tools does that already)

Hm, I see. Thanks, I'll give it a go, and hope for the release of the functional api in core.

is there something like s/cat but that doesn't do any labeling? need to match a subsequence within a sequence without too much ceremony

it's a seq of chars (just playing), so nothing generic, I need equality matching (ex match (b a r) in (f o o b a r b a z))

I know I can mix s/cat and sets of chars or predicates, but that's quite ugly

I am also forced to use regex context (my question is part of a wider parsing thing)

if you don’t want labeling, just use s/valid?

I dont need labeling per char, I do for the whole subseq (up one level)

maybe I didn't understand what you mean

all the surounding value have a meaning that I need to retain also, I can't just check "does this seq contains this sub-seq"

you can use s/& to apply a custom predicate to a regex spec

which could be helpful here

right, forgot about &

that's brilliant, I was messing with conformers but I think & might just do all this for me

is it just me or do tools.namespace and instrument not get along?

or does it not check things that are defed?

that is, if I reload a namespace that has (def foo (some-instrumented-fn invalid-value)), does reloading the ns throw an exception?

Reloading is going to remove your instrumented vars

ok, so those checks should be done through tests instead?

what checks?

let me change the question: what’s the best way to check specs with clojure.test?

that seems pretty far from the original questions :)

(is (s/valid? ::my-spec (some-fn)) works, but it doesn’t give helpful output

I’m not very familiar with either clojure.test or spec, so I’m fumbling around a bit 🙂

there used to be a pin here to an example, but maybe it has aged out

by “check specs”, I’m assuming you mean to run clojure.spec.test.alpha/check on one or more spec’ed functions

actually, I want to check with s/valid?, but use s/explain instead of the usual error message provided by is

so s/valid? is not going to be as useful in checking spec’ed functions as is calling check

unless ::my-spec here refers to a data spec

I can’t really tell

::my-spec in this case is a data spec, yes

ok

sorry if my questions are a bit confused, it’s hard to ask good questions when you’re not familiar with something

yep, no worries

I am similarly trying to re-interpret your questions :)

so you want to check if some data matches a spec and if not, return a message that is s/explain

one way would be to:

(is (nil? (s/explain ::spec data)))

although I guess you want the explain result as a value not as a print

(is (not= "Success!\n" (s/explain ::spec data))) would do that I think

that’s quite ugly of course :)

explain-data did the trick!

yeah, can do same idea with explain-data

you can supply a final custom error message to is too

so something like: (is (valid? ::spec data) (s/explain-str ::spec data)) ?

I went with this:

(defmacro spec-is [spec value]
  `(is (nil? (s/explain-data ~spec ~value))))

thanks a ton for your help! 😄

np!