Extended ConsoleLogger prints undefined on every log message about nest

[czioutas]

I updated the reproduce repo with a logSafe function which essentially checks if context is undefined before sending it to super.
I assumed that this functionality would be handled from the core logic.
app-logger.service.ts

  logSafe(message: any, context?: string) {
    const modifiedMessage = `${message} test`;

    console.log(modifiedMessage, context);

    if (context === undefined) {
      super.log(modifiedMessage);
    } else {
      super.log(modifiedMessage, context);
    }
  }

[kamilmysliwiec]

nest/packages/common/services/console-logger.service.ts

Lines 67 to 78 in 033f181

	log(message: any, context?: string): void;
	log(message: any, ...optionalParams: [...any, string?]): void;
	log(message: any, ...optionalParams: any[]) {
	if (!this.isLevelEnabled('log')) {
	return;
	}
	const { messages, context } = this.getContextAndMessagesToPrint([
	message,
	...optionalParams,
	]);
	this.printMessages(messages, context, 'log');
	}

Since log() method lets you pass multiple messages (separated by ,) to write to the stdout, second parameter won't necessarily represent a "context" (https://github.dev/nestjs/nest/blob/033f18161fb4d391aab0dac22f71209b97c94993/packages/common/services/console-logger.service.ts#L295) - that's why undefined is logged down too. While this may not be the most straightforward, we can't really do anything on our side without introducing a breaking change