Add support for log levels. Fixes #51 #80
Merged
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.
Description
The PR introduces the ability to display/hide logged messages through a scaled logging level system. The logging level can be defined through the
logLevel
option, which is of typeString
& it is part of the configuration object pass to the initialization of aSignale
instance, and can be one of the following 5 strings:'info'
- Displays all the messages of all logger types.'timer'
- Displays only the messages oftime
,timeEnd
,debug
,warn
,error
&fatal
logger types.'debug'
- Displays only the messages ofdebug
,warn
,error
&fatal
logger types.'warn'
- Displays only the messages ofwarn
,error
&fatal
logger types.'error'
- Displays only the messages oferror
&fatal
logger types.The default value is
'info'
for thelogLevel
Signale configuration option, as well as for thelogLevel
attribute of custom logger types. The option is inherited from parent to child instance whenever the unarysignale.scope()
function is used.