Feature request: change visibility from private to protected to allow overrides

[zirkelc]

Use case

As discussed before, I would like to suggest to change the visibility of certain methods of Logger from private to protected to allow overrides by subclassing Logger. A use case for such an override would be the buffering of log messages (see #3178).

If approved, I'm happy to submit a PR.

Solution/User Experience

The following methods could be made protected:

powertools-lambda-typescript/packages/logger/src/Logger.ts

Lines 703 to 707 in 0dc4de1

	private createAndPopulateLogItem(
	logLevel: number,
	input: LogItemMessage,
	extraInput: LogItemExtraInput
	): LogItem {

powertools-lambda-typescript/packages/logger/src/Logger.ts

Line 838 in 0dc4de1

private printLog(logLevel: number, log: LogItem): void {

powertools-lambda-typescript/packages/logger/src/Logger.ts

Lines 865 to 869 in 0dc4de1

	private processLogItem(
	logLevel: number,
	input: LogItemMessage,
	extraInput: LogItemExtraInput
	): void {

Alternative solutions

Acknowledgment

• This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[dreamorosi]

Hi @zirkelc, the proposal makes sense.

We discussed this in #3178, so feel free to open a PR to make these changes and I'll help you get it merged before the next release!

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v2.12.0 version!