-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Update to pretty 0.1.34 #355
Comments
@hlship Thanks for the heads up! You're right about the versions, perhaps adding them to the namespace meta would be good? Like this perhaps: (ns boot.from.io.aviso.ansi
{:boot/from :AvisoNovate/pretty:0.1.20
:doc "Help with generating textual output that includes ANSI escape codes for formatting."} |
Eventually it would also be good to use some more automated way to handle these libraries. Either by 1) moving them to |
I may work on this on friday (our "fun day"). |
Is the fact that current Pretty changes the order of output going to be a problem? Basically, normal Java stack traces are backwards (each successive line is further back in time). More recent versions of pretty invert this by default. Basically, clojure.main at the top of the stack trace, your.task.here at the bottom. |
Personally I have always preferred the relevant info on the bottom in the console, so good for me 😄 |
Pretty is at Equally worthwhile work would be the inlining boot task Juho mentioned above. |
I got this one 😉 |
PR opened #670 |
pretty 0.1.20 adds support for Clojure 1.8; specifically, support for deep-linked functions.
For these "imported" libraries, it would be nice if there was a single place to check to see what version is effectively incorporated.
The text was updated successfully, but these errors were encountered: