Update logger.js to not use eval #1
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
|
Yeah it doesn't work - it logs everything at LOGEMERG level, which is why I found I had to use the eval. |
Merged
This was referenced Oct 23, 2016
This was referenced Mar 11, 2017
This was referenced Apr 7, 2017
Closed
msimerson
referenced
this pull request
in msimerson/Haraka
Aug 25, 2017
This was referenced Oct 10, 2017
This was referenced Jan 19, 2021
Closed
This was referenced Apr 27, 2023
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.
Used the object property to setup the calling function and formatted log messages to display log type in square brackets.