[patch] Allow log prefixes to be properly disabled when using custom logger #15
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.
See
issue #14EDIT: Moved to sails#4036.These changes create the following behavior (I made sure to test each scenario described below):
Without a custom logger, everything should work the same, except that it only sets the default prefix if
options.prefix
is notfalse
ornull
.With a custom logger and no prefix defined, no prefixes are set and relies on the custom logger to handle its on prefixes (probably preferred behavior with most custom loggers).
With a custom logger and
options.prefix
defined totrue
it adds the default prefixes before passing the message to the custom logger (this option might result in duplicate prefixes like described in the issue if the custom logger has its own prefixes, but it would be useful if the custom logger did not have it's own prefixes).With a custom logger and options.prefix is defined as a string, the string prefix is prepended to the message sent to the custom logger.