Add clarification on log package for logging #16
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the target audience for your overview (proficient in node, but beginner in Go) I was delighted to see all the examples. But I stumbled on an error, or so I thought 🙈
As the Logging example was omitting the timestamp in the code (as is part of the node example), I wanted to 'fix' that Logging Go example with:
..only to find out that the log package already automagically includes the timestamp! 🎉 😮
For people moving from node to Go this is totally not obvious, so I thought it is very nice to explain that to prevent others from making the same assumption.