Using the SaxonJS.transform logLevel option sets the log level globally
Running the nodejs unit tests, I've noticed that setting the
logLevel transform option sets this level globally, rather than just for that transform. This is not really what we want.
Updated by Debbie Lockett over 1 year ago
- Status changed from New to In Progress
I have added
context.fixed. This is set for transforms using the value supplied for the
logLevel option, or defaults to the value of
SaxonJS.getLogLevel() (which has default 1, or can be set globally using
contextLogLevel is added as a parameter to
Diag.saxonPrint() so that this method can determine whether the log is to be output or not. All
Diag.saxonPrint() calls for warning and processing logs should supply both "level" and "contextLogLevel" arguments, but when using
Diag.saxonPrint() for temporary internal diagnostic logs these can both be omitted.
Unit test nodejs
async-trans-035 demonstrates that asynchronous transforms run in parallel can have different log levels, with expected results.
Committed to saxonjs2 and main branches.
Please register to edit this issue