-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Feature: Add slog compatibility layer #1401
Labels
Comments
Would love to see this accepted in core logrus also. |
This issue is stale because it has been open for 30 days with no activity. |
I've begun work on this, and intend to create a PR before too long. |
This issue is stale because it has been open for 30 days with no activity. |
Open
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know this project is in maintenence mode, but I think it would be worth making an exception to the "no new features" rule to add a simple
slog
compatibility layer, as the alternative is some minor chaos when others create competing implementations, and inevitably abandon them.This could take one, or even two, forms:
slog
hook for Logrusslog
I would be happy to take this on and write the code (I have a partial implementation already completed for a client I'm working with).
The text was updated successfully, but these errors were encountered: