-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Better log output #4
Comments
We've done |
I like a JSON format, because you could copy/paste it right into a REST client. Maybe the headers should also be logged? |
As it seems, all newlines are stripped when using the |
Turns out Monolog can have different formatters, and you can make your own. Laravel also has its wrapper around this: I didn't go as far as making our own formatter, but it seems like a possibility, enabling new lines. I don't think it's worth the time now, but might be a nice feature for the future. |
I very much like this idea. |
@freekmurze But the question about formatting in the log output itself still stands. What's your opinion? To format the JSON in a pretty way, we'll have to create a custom formatter. Functionally the unformatted JSON output will of course work just as fine; so pretty format might not be that important. |
It would be nice to separate concerns of
This way regardless of logger/formatter requests that shouldn't be logged won't be. |
That's a pretty good idea, let's do that @brendt . |
Confused, isn't that what it looks like now? 🤔 |
I share @sebastiandedeyne's confusion, or were you maybe @pmatseykanets was referring to further split it in separate classes? |
Separating concerns will be handled in #7 Current log output is good enough for a v1.0.0 |
Currently, the log output is just a single line. There might be a better format.
Opinions are welcome.
The text was updated successfully, but these errors were encountered: