put nodejs resource registration logs behind excessiveDebugOutput flag (#7144)
This commit is contained in:
parent
85142462c7
commit
d0d4e2d7d9
|
@ -631,7 +631,9 @@ export function register<T extends { readonly version?: string }>(source: Map<st
|
|||
// In this case, we might legitimately get mutliple registrations of the same resource. It should not
|
||||
// matter which we use, so we can just skip re-registering. De-serialized resources will always be
|
||||
// instances of classes from the first registered package.
|
||||
log.debug(`skip re-registering already registered ${registrationType} ${key}@${item.version}.`);
|
||||
if (excessiveDebugOutput) {
|
||||
log.debug(`skip re-registering already registered ${registrationType} ${key}@${item.version}.`);
|
||||
}
|
||||
return false;
|
||||
}
|
||||
}
|
||||
|
@ -640,7 +642,9 @@ export function register<T extends { readonly version?: string }>(source: Map<st
|
|||
source.set(key, items);
|
||||
}
|
||||
|
||||
log.debug(`registering ${registrationType} ${key}@${item.version}`);
|
||||
if (excessiveDebugOutput) {
|
||||
log.debug(`registering ${registrationType} ${key}@${item.version}`);
|
||||
}
|
||||
items.push(item);
|
||||
return true;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue