Added support for passing a function/closure to the logger #424
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.
Added support for passing a function/closure to the logger as a message instead of a raw string. This allows log messages to be lazily evaluated only when actually emitted (which can yield substantial performance benefits). This was already possible using logging level-based conditional logging, but the syntax was much messier:
vs
logger.trace(() => JSON.stringify(myBigObject));