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.

Sign up for GitHub

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

Jump to bottom

Add logging #3547

Closed
colejohnson66 opened this issue Nov 4, 2016 · 2 comments
Closed

Add logging #3547

colejohnson66 opened this issue Nov 4, 2016 · 2 comments

Comments

@colejohnson66
Copy link

For a project of this size, logging seems like a must. Especially with bugs such as #2151. I recently had a consistent repro on Windows 10 64-bit in Chrome 56.0.2896.3 dev, but now that it's updated to 56.0.2906.0 dev, I no longer can consistently repro that bug. If there was a flag, say debug=true in the URL, then people who can consistently repro issues could post a log dump for those who can't.
@bhousel
Copy link
Member

bhousel commented Nov 4, 2016

What would you want logged? Chrome already includes a really great code profiler that can trace all the JavaScript calls. It just seems like you'd get far more information by using the tool than from anything we could write to the console.log.

For a project of this size, logging seems like a must.

How big do you think this project is? 😁

@bhousel
Copy link
Member

bhousel commented Nov 8, 2016

Closing, because as mentioned above, all the developer tools are great at code profiling and tracing.

@bhousel bhousel closed this as completed Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bhousel @colejohnson66