Make millisecond timer namespace specific and allow 'always enabled' output by gtjoseph · Pull Request #408 · debug-js/debug
and others added 2 commits
December 30, 2016 07:22When debugging node apps, I find it much more useful for the millisecond timer to be relative to last message from the same namespace instead of any message. This is especially true when I'm debugging across multiple libraries or multiple levels in the same module and I'm interested in seeing all the messages but also need to compare times from specific levels.
Having to deal with 2 different logging mechanisms, one for debugging
and one for normal output, can be a nuisance. It would be much easier to
always use the same facility and semantics for both. This patch allows
an 'always enabled' namespace to be specified by appending a single '*'
to the namespace name.
var alwaysOn = require('debug')('normal:messages*');
alwaysOn('This will always display regardless of DEBUG');
gtjoseph
changed the title
Make millisecond timer namespace specific
Make millisecond timer namespace specific and allow "always enabled' output
gtjoseph
changed the title
Make millisecond timer namespace specific and allow "always enabled' output
Make millisecond timer namespace specific and allow 'always enabled' output
thebigredgeek pushed a commit that referenced this pull request
Apr 12, 2017…output (#408) * Make millisecond timer namespace specific When debugging node apps, I find it much more useful for the millisecond timer to be relative to last message from the same namespace instead of any message. This is especially true when I'm debugging across multiple libraries or multiple levels in the same module and I'm interested in seeing all the messages but also need to compare times from specific levels. * Enable 'always enabled' output Having to deal with 2 different logging mechanisms, one for debugging and one for normal output, can be a nuisance. It would be much easier to always use the same facility and semantics for both. This patch allows an 'always enabled' namespace to be specified by appending a single '*' to the namespace name. var alwaysOn = require('debug')('normal:messages*'); alwaysOn('This will always display regardless of DEBUG');
TooTallNate pushed a commit that referenced this pull request
Aug 8, 2017…output (#408) * Make millisecond timer namespace specific When debugging node apps, I find it much more useful for the millisecond timer to be relative to last message from the same namespace instead of any message. This is especially true when I'm debugging across multiple libraries or multiple levels in the same module and I'm interested in seeing all the messages but also need to compare times from specific levels. * Enable 'always enabled' output Having to deal with 2 different logging mechanisms, one for debugging and one for normal output, can be a nuisance. It would be much easier to always use the same facility and semantics for both. This patch allows an 'always enabled' namespace to be specified by appending a single '*' to the namespace name. var alwaysOn = require('debug')('normal:messages*'); alwaysOn('This will always display regardless of DEBUG');
TooTallNate pushed a commit that referenced this pull request
Aug 8, 2017…output (#408) * Make millisecond timer namespace specific When debugging node apps, I find it much more useful for the millisecond timer to be relative to last message from the same namespace instead of any message. This is especially true when I'm debugging across multiple libraries or multiple levels in the same module and I'm interested in seeing all the messages but also need to compare times from specific levels. * Enable 'always enabled' output Having to deal with 2 different logging mechanisms, one for debugging and one for normal output, can be a nuisance. It would be much easier to always use the same facility and semantics for both. This patch allows an 'always enabled' namespace to be specified by appending a single '*' to the namespace name. var alwaysOn = require('debug')('normal:messages*'); alwaysOn('This will always display regardless of DEBUG');
This file contains hidden or 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