| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
According to MDN history, it's called timerName on there since 2012 when that article was created, thought calling it label seems somewhat common too.
If we agree on calling it label, I can change it on MDN, supposedly.
cc: @targos
Sorry, something went wrong.
There was a problem hiding this comment.
@silverwind I don't really care. I changed it after your suggestion.
If you want to change it back, just run git revert 8c043c1
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
@silverwind done.
Sorry, something went wrong.
- changed node's console doc to follow the following spec doc - https://github.com/DeveloperToolsWG/console-object/blob/master/api.md
|
LGTM |
Sorry, something went wrong.
There was a problem hiding this comment.
The first argument is optional too. You can call console.log() to print a blank line.
Sorry, something went wrong.
There was a problem hiding this comment.
I've tested this before, Node and Firefox print an empty line, Chrome does not. Maybe it should be brought up with the spec authors?
Sorry, something went wrong.
There was a problem hiding this comment.
Meh, what actually matters here is what Node does.
Sorry, something went wrong.
There was a problem hiding this comment.
Should be console.log([object, ...]), I think.
Sorry, something went wrong.
There was a problem hiding this comment.
Or console.log([object [, ...]]) ?
Sorry, something went wrong.
There was a problem hiding this comment.
Like in PHP doc: http://php.net/manual/en/function.printf.php
Sorry, something went wrong.
|
@Fishrock123 agree, this isn't correctly documenting how it currently works in node. I filed DeveloperToolsWG/console-object#36 to hopefully clarify what the expected behaviour is. |
Sorry, something went wrong.
|
That "spec" is a reasonable attempt but not really anything normative. I would not base anything on it. Console behaviour is not really interoperable. |
Sorry, something went wrong.
|
@domenic are you saying that our console shouldn't try to be similar to a browser console? |
Sorry, something went wrong.
|
It definitely should. But that document and browser console behavior are unrelated. And browsers don't really agree on console behavior in various ways. |
Sorry, something went wrong.
|
Marked as stalled. Will close if there's no new activity in the next few weeks. |
Sorry, something went wrong.
|
Closing due to further lack of activity. This might still be worthwhile, however, so can definitely reopen if necessary. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.