include log level in log line #7
Closed
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
arv
reviewed
Mar 22, 2022
| // This really isn't the right place to put the log level tag, we should instead | ||
| // have a formatter that can be passed to a logger (including the consoleLogger) | ||
| // and we can then use that formatter regardless of where the log is going. | ||
| console[level](logLevelTag[level], ...args); |
There was a problem hiding this comment.
I don't like this. console.log already outputs these with differently:
I guess what you want is for nodejs to output them differently. Maybe add a specific nodejs LogSink?
There was a problem hiding this comment.
ok try #9 on for size. i bumped the version as part of that change, but did not publish a new package (wanted to wait for you to give the thumbs up).
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.
No description provided.