-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For function specs, show which spec failed. #13
Comments
@jeaye You read my mind 😄. This is something I hope to complete sometime this week. I'm not 100% sure yet how to format the error, but it's something I want to support. Would you mind giving me feedback when I have a draft version? |
Sure thing; let me know when you have a snapshot version, or branch or whatever you prefer, and I'll give it a shot. Thanks for the quick reply! |
I still need to do some more dogfooding on this, but I have something you can try when you have some time:
The relevant tests are here |
Thanks for the update; I can give this branch a shot in the next few days and I'll let you know how it goes.
|
Excellent, thanks very much for your help! |
I've just given this branch a go with our ClojureScript app and have introduced the various Thank you for the explicit orchestra support; I'm looking into the |
Glad to hear it! Thanks very much for trying this out. I'll do a release this week. |
I have released version 0.2.0 which includes this feature. Thanks for the help! https://clojars.org/expound/versions/0.2.0 |
Thank you! |
When instrumenting, especially with orchestra, expound provides less information than clojure.spec would, since it doesn't say whether or not it was the
:ret
or:args
or:fn
that failed to validate.Are you open to adding this support?
The text was updated successfully, but these errors were encountered: