Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom log levels #89

Closed
tizu69 opened this issue Nov 12, 2023 · 0 comments · Fixed by #95
Closed

Custom log levels #89

tizu69 opened this issue Nov 12, 2023 · 0 comments · Fixed by #95
Labels
enhancement New feature or request

Comments

@tizu69
Copy link

tizu69 commented Nov 12, 2023

I'd like to add my own log levels. How would I do this?

@aymanbagabas aymanbagabas added the enhancement New feature or request label Nov 27, 2023
aymanbagabas added a commit that referenced this issue Nov 27, 2023
Exposing `logger.Log` makes it possible to use a custom log level to log
messages. Simply define a new level and use `Log` and `Logf` to log
messages using the newly defined level.

Fixes: #89
aymanbagabas added a commit that referenced this issue Dec 7, 2023
Exposing `logger.Log` makes it possible to use a custom log level to log
messages. Simply define a new level and use `Log` and `Logf` to log
messages using the newly defined level.

Fixes: #89
aymanbagabas added a commit that referenced this issue Dec 7, 2023
Exposing `logger.Log` makes it possible to use a custom log level to log
messages. Simply define a new level and use `Log` and `Logf` to log
messages using the newly defined level.

Fixes: #89
Malanris pushed a commit to Malanris/plog that referenced this issue Jul 29, 2024
Exposing `logger.Log` makes it possible to use a custom log level to log
messages. Simply define a new level and use `Log` and `Logf` to log
messages using the newly defined level.

Fixes: charmbracelet/log#89
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants