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

feat: support setting global max_level #63

Merged
merged 2 commits into from
Oct 9, 2024
Merged

feat: support setting global max_level #63

merged 2 commits into from
Oct 9, 2024

Conversation

tisonkun
Copy link
Contributor

@tisonkun tisonkun commented Oct 9, 2024

No description provided.

@@ -192,7 +204,6 @@ impl log::Log for Logger {
}
}

// TODO(tisonkun): logback and log4j2 support custom error handling (status listener).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andylokandy I finally tend not to add something like ErrorListener or StatusListern for customizing error handling.

The current hard code behavior works well and I don't find any other way to "customize" it. If there is some real requirement (and it's always doable), we can add it later, instead of providing a public interface at this point.

@tisonkun tisonkun changed the title feat: support setting global max_level feat: support setting global max_level Oct 9, 2024
@tisonkun tisonkun merged commit 3007fde into main Oct 9, 2024
5 checks passed
@tisonkun tisonkun deleted the random branch October 9, 2024 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant