When i'm reading expound formatted spec errors it's usually very clear what the issue is, it's not immediately clear where the error is. This information: the filename, and possible the row and column. Is in the raw spec error output as well as the SO, but they can be far from the expound message. In the case of the raw spec error, is just a big clojure map that's tiresome to parse.
My suggestion is to either always include that information nearby so it's easy to find. Maybe something like:
-- Spec failed --------------------
1
should satisfy
string?
Found in foo.main:67:3:2
-------------------------
I'm not really sure what the UI should be exactly. maybe even in the header like:
-- Spec failed at foo.main:67:3:2 --------------------
When i'm reading expound formatted spec errors it's usually very clear what the issue is, it's not immediately clear where the error is. This information: the filename, and possible the row and column. Is in the raw spec error output as well as the SO, but they can be far from the expound message. In the case of the raw spec error, is just a big clojure map that's tiresome to parse.
My suggestion is to either always include that information nearby so it's easy to find. Maybe something like:
I'm not really sure what the UI should be exactly. maybe even in the header like:
-- Spec failed at foo.main:67:3:2 --------------------