-
Notifications
You must be signed in to change notification settings - Fork 3
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
No trace no more #2
Comments
By the way I found a workaround, and I don't think I added: |
That's not a workaround, that's expected behaviour :). You need to provide a closure-define to enable/disable it IIRC. |
Oh, but the pure |
@arichiardi we provided the original patch to clairvoyant so it would use But the bottom line is that our fork is subtly different on that point. And, sorry, you are right that a note in the README would be a good idea. |
Oh (#2), sorry about the noise guys, I was a bit out of the loop on this. Of course it explains everything and thanks for clarifying it. I will add the note. |
Thanks for pointing this out and improving the README. We've improved the originating docs too. |
I was using this library with success in
lein
, switching toboot
muted the tracing.I am not even sure that the
lein
toboot
passage is related, but basically after a bit of debugging I see thatjs/clairvoyant.core.devmode
is always false no matter what:elide-asserts
is.I wanted to dig more and I migth be blind but I cannot really find where
clairvoyant.core/devmode
is defined in the code source.I need some little hint 😄
The text was updated successfully, but these errors were encountered: