-
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
Internal Expound assertion failed using ring.core.spec #93
Comments
@conan Thanks very much for reporting this! It appears to be a bug in Expound. |
Some changes in 0.7.1-SNAPSHOT make this slightly better - instead of giving an error, expound prints the (confusing, at least to me) error message:
I'm going to leave this open until I can look into this more. For reference, a test that reproduces the issue for me:
|
Hm, this may relate to over-using the internal function |
Related: ring-clojure/ring-spec#7 |
@conan Thanks for reporting this. This fix is included in version 0.8.0, which I've just released. |
I've written a function spec for my top-level ring handler, which is a function called
app
that callsreitit.ring/ring-handler
. It looks like this:The
:ring/handler
spec is defined in ring-spec.There's some kind of problem when I call (or
s/explain
the result of) this function that makes Expound throw an exception. It looks like this:(this is how it's formatted)
When I run without expound, I get the following output:
Now I have no idea what's up with the spec or why Expound throws an exception, but clearly the raw spec formatting is preferable.
The text was updated successfully, but these errors were encountered: