Fork me on GitHub
#clojure-spec
<
2016-07-31
>
gfredericks03:07:07

that's a nice explanation

seancorfield03:07:38

(I’m just repeating what Stu said in the latest Cognitect clojure.spec 'cast! 🙂 )

gfredericks18:07:27

in particular if you're running check while instrumenting with stubs

gfredericks18:07:17

I don't think there's as straightforward a fix as in CLJ-1949 though

gfredericks18:07:07

probably the cleanest thing would be a private dynamic var somewhere for registering quickcheck-driven generation fns

gfredericks18:07:22

it could use gen/generate as the default when you're not actually running a test.check test

gfredericks18:07:22

shall I make a ticket?

lvh22:07:17

@gfredericks: FYI, I made a bunch of progress on the JSON Schema thing, knocking a few remaining ones down; the really really hard one is references (idk if you’re familiar with JSON schema, but basically you have a base URL and URL-y internal/external references, so you need a way to resolve things like #../../xyzzy/0 or whatever). Dunno if it’s going to be of a size where it’s interesting for spec, but we’ll see

lvh22:07:10

Are you interested in like, mostly-working-but-missing-stuff impls, or would you rather just pull in an entire impl when it’s done, or rather have it live in its own package

lvh22:07:38

It’s currently about 250 lines of impl and 220 of test; that’ll probably go up to 300

lvh22:07:03

it doesn’t have any particularly weird deps, but to do it Right(TM) you need test-chuck’s regex generator