-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
Pretty Printing Exceptions in cider-test #1873
Comments
Is your issue similar to #1707 ? I'm not sure what exactly are you suggesting that we should pretty-print. |
@bbatsov Similar error, (in fact I am using schema as well). I'm wondering if it's possible to take that exception object and pretty print it because the map object is quite big. |
The problem is that this is just plain text in the exception message and here's no way to know what's a Clojure object there and what is not... |
Is there a way to tell whether the exception is an Clojure itself tends to be pretty consistent in using |
Perhaps, I don't have any time to research this. If someone else would like to tackle it - be my guest. :-) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding! |
When I'm working with
cider-test
and a test throws aex-info
with a large data structure (i.e. working with prismatic.schema), it's always printed in a single line (regardless if I have pretty-printing enabled or disabled).If we had the ability to pretty-print these objects, it would make inspecting large objects easier.
The text was updated successfully, but these errors were encountered: