> It might be worth including a discussion about when to use this library,
and perhaps indicating that using it might not be a best-practice.
I'm using it to instrument a running development system as I'm working with
it, via an API, REPL, and tests. I've found it handy in all three places
for my
I find it funny that Clojure strongly believes that static types aren't worth
the effort in most cases, but somehow the effort of adding generative testing
is.
I think it's great to encourage people to use generative testing, but I'd
rather it be à la carte, like most other things in Clojure. O
It might be worth including a discussion about when to use this library,
and perhaps indicating that using it might not be a best-practice.
:ret and :fn specs were originally validated by instrument, but this
feature was removed because Rich et al thought it redundant, and that there
were differen
Thanks Jeaye, I'm really happy to see this for CLJS too!
Orchestra has been an excellent development time addition to our apps.
Checking the :ret specs is very helpful for finding the error in code as
close as possible to the problem, rather than further downstream when a
further spec fails.
On S
Folks,
I'm happy to announce that a new version of Orchestra has been released this
past week.
# Where to find it?
https://github.com/jeaye/orchestra
[orchestra "2017.07.04-1"]
# What is it?
Orchestra is a Clojure(Script) library made as a drop-in replacement for
clojure.spec.test.alpha, which
