Cleaner log functions #64
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Instead, this is set when we require the logger and have it automatically insert the filename.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The logging functions now automatically insert
[nodecg/lib/example]rather than needing it in every log statement. This filename string is instead set when we require the logger;require(../logger)('blah')gives all messages the[blah]prefix.I have also changed out log statements to begin with
nodecg/, with the idea that extensions should get access to our logger with the (automatically set) prefix[bundleName/path/to/extension.js]. Addingnodecgto our statements should help someone visually filter between system and extension messages quickly.