Feature request: Narrow LogLevel type to not allow arbitrary strings

[danrivett]

Use case

Raising this ticket after the discussion in #1198.

Currently the LogLevel type allows for any string to be used, but at runtime it validates the value and if it doesn't match one of the valid log levels (as per isValidLogLevel()) it silently ignores the log level passed in and uses the default.

This has two problems:

1. The issue isn't caught at compile time
2. The passed in log level is silently ignored which may not be detected.

Regarding 1. above, the following typo currently compiles. It would be better for the typo to be detected at compile time:

const logger = new Logger({ logLevel: 'DEBG' });

Solution/User Experience

Narrow the LogLevel type definition, removing the | string part.

Alternative solutions

No response

Acknowledgment

• This feature request meets Lambda Powertools Tenets
• Should this be considered in other Lambda Powertools languages? i.e. Python, Java

[dreamorosi]

Hi Dan, thank you for opening the issue.

I think this is a valuable addition to the logger, I'll be working on this.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.

[dreamorosi]

This change was released as part of the latest v1.6.0 release.