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

Additional questions #6

Closed
AnnJohn opened this issue Jun 15, 2016 · 0 comments
Closed

Additional questions #6

AnnJohn opened this issue Jun 15, 2016 · 0 comments
Assignees

Comments

@AnnJohn
Copy link
Contributor

AnnJohn commented Jun 15, 2016

Really like that this is pared down more --

A couple of comments. When you first talk about 'console' you write "What methods does console expose? " Students do not know what methods yet mean.

I get a good grasp of console.log because it's just printing out stuff to the screen.

I understand less well console.warn and console.error -- I think my biggest questions are why/when will they happen. I know the mechanics of typing them to the console but I'm not sure how this actually works. Is there a little bit of context that you can provide? Or maybe an example. For example, having a scenario where this would appear would be helpful "console.error() prints an error and usually includes a stack trace. "Stack traces" is a report of code that was executed at a certain time (in this case, starting from when the error occurred and working backwards). Enter the following in your console:"

Otherwise, this is pretty good.

@jmburges

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