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.
Motivation
I personally would like to remove minified error message 1 (see #1161), and others have expressed their desire to completely suppress logging.
With this solution, both are possible.
How It Works
A new utility module named
logging
has been added to thesrc/utils
folder that exports 2 objects:setLogger()
function that controls the destination of all log entries.logger
object, whose methods write to the log destination set bysetLogger()
.By default, the log destination is the console. Users can, at any point in their application's lifecycle, call
setLogger()
to control which log entries make it to the browser's console.setLogger()
This function takes 1 argument that can be
false
,true
or a custom destination log object.The value
false
internally sets a log destination that discards all messages; the valuetrue
routes all messages to the console. The third option allows the caller to take complete control over what to do with the logged messages.For Maintainers and Contributors
Never do
console.debug()
,console.info()
,console.warn()
orconsole.error()
ever again. Always replaceconsole
withlogger
. Logger is imported: