Skip to content
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

Reduce logging output or maybe create logging levels? #30

Closed
seantempesta opened this issue Mar 20, 2016 · 3 comments
Closed

Reduce logging output or maybe create logging levels? #30

seantempesta opened this issue Mar 20, 2016 · 3 comments

Comments

@seantempesta
Copy link

Right now re-natal logs a lot of info to the console. It's easy to get lost in the sea of cljs packages that are loaded and evaled (two separate messages per file). Maybe removing some of the logging would help users see more signal than noise? Here's what my console looks like after I disabled some of the info logs:

screen shot 2016-03-20 at 2 55 04 pm

Beautiful! :)

@drapanjanas
Copy link
Owner

Looks nice indeed. I will think about how to implement disable/enable extensive logging. Two lines for each js files were neded because in case of debugging in chrome the files are loaded synchronously one by one, and when not in browser - asynchronously, first queued and then evaled using eval function. In case of some strage problems IMO you still might want to know in what sequence your files are loaded.

@seantempesta
Copy link
Author

Yeah, I hear ya. Maybe a var debug = true; if(debug) {...} would suffice?

@drapanjanas
Copy link
Owner

Hey, I think it would! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants