allow filtering of message components #3

New issue

Closed

opened 2012-10-30 19:33:13 +02:00 by nodify · 0 comments

nodify commented

2012-10-30 19:33:13 +02:00

(Migrated from github.com)

in a blatant rip-off of VMS's message utility, nodify-logger messages look like this:

%FACILITY-S-ABBREV:TIMESTAMP; MESSAGE.

Each of these components should be able to be turned on or off, maybe with a function call like this:

require( 'nodify-logger' ).createInstance( { ... options ... }, function( _f, _m, _i ) {
_f( _m, I_EVERYTHING );
_i.components( "FACILITY,SEVERITY,ABBREV,MESSAGE" );
_f( _m, I_NODATE );

... more code ...
} );

this could should spit out the following errors:

%SHIZZLE-I-EVERYTHING:2012-10-30T10:30:00Z; This message should have a date.
%SHIZZLE-I-NODATE; This message should not have a date.

in a blatant rip-off of VMS's message utility, nodify-logger messages look like this: %FACILITY-S-ABBREV:TIMESTAMP; MESSAGE. Each of these components _should_ be able to be turned on or off, maybe with a function call like this: require( 'nodify-logger' ).createInstance( { ... options ... }, function( _f, _m, _i ) { _f( _m, I_EVERYTHING ); _i.components( "FACILITY,SEVERITY,ABBREV,MESSAGE" ); _f( _m, I_NODATE ); ... more code ... } ); this could _should_ spit out the following errors: %SHIZZLE-I-EVERYTHING:2012-10-30T10:30:00Z; This message should have a date. %SHIZZLE-I-NODATE; This message should not have a date.