-
Notifications
You must be signed in to change notification settings - Fork 52
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
Provide a default print-logger #61
Comments
See also #12 I do think there is some room for shipping utilities like this, probably under a separate import. The blocker here is that it's not clear to me we could provide something that satisfies enough users to make it worthwhile - the log listeners and formatters that I've come across generally have some subtle or major differences that are hard to rectify... |
I would prefer to have the default logger push out just the error message to |
Most use cases I'm aware of would probably prefer Most likely what we'd need in order to accept a standard logger or formatter into this package is buy in from a sufficient number of stakeholders with agreement on a behavior and format. That means coordinating with existing first party tools using this library (tools in the SDK, A better approach might be to ship something in a separate package, and drive consensus from the bottom up. |
fwiw, I've published a simple logging appender package a while ago which is basically |
I think it could be very useful to provide a print-logger function that can be registered as a listener to the log stream. The current one-liner that's in the example doesn't log the
.error
and.stackTrace
variables, so many people that just pastes it in will probably not get that information in their logs.I'm thinking something like this:
or maybe even:
Would be happy to submit pull requests if we know what we want :)
The text was updated successfully, but these errors were encountered: