-
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
expound-printer #4
Comments
@olivergeorge Agreed! I've got a local branch where I'm working on this now. |
@olivergeorge Do you mind trying this feature before I release? To try it:
|
The output during instrumentation could be optimized for that use case, but I'll leave that for a further PR. |
Thanks for reporting this! |
We just tested it in on our code (cljs preload) and it's working like a charm. |
@olivergeorge I'm glad to hear that. At some point I'm going to do more work on presenting the failure in a better way (including the source code and line numbers). |
It'd be nice to be able to bind expound-str to
s/*explain-out*
. With that stest/instrument should present expound formatted descriptions in exceptions.The main difference to the current code is that
*explain-out*
printers take explain-data as an arg.The text was updated successfully, but these errors were encountered: