-
Notifications
You must be signed in to change notification settings - Fork 29
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
Please add fatal #44
Comments
Also, would you please add 'warn' as well as 'warning'? |
The docs say that "We also allow 'warn' as a synonym for 'warning'" already, so if it's not working, that's a bug. As for compatibility with other logging systems, isn't that what Log::Any is for? If it's still desirable to put it in Log-Dispatch, then it'd probably be good to do the same mapping as it does (which is, yes, |
I think I agree with preaction that if you need compatibility between logging systems then |
This is for Log::WarnDie, so I don't see how that would help. |
The Log::WarnDie docs say "Any object that provides a I think Log::Any is a better solution for Log::WarnDie: If you want to log to files or syslog or Mojolicious or other facilities, you don't need to take the middle step of using Log::Dispatch and setting up its output handles. You just directly configure the output adapters on the Log::WarnDie object. If all else fails, a quick [1]: People have been giving me maintainership of adapters left and right, so if any don't work with Log::WarnDie, I probably have the permissions needed to fix them. |
Please add a 'fatal' method which should be the same as 'critical'. This would add compatibility with Log::Log4perl.
The text was updated successfully, but these errors were encountered: