-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Colors no longer show in middleware.Logger output #1417
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
So because there is no activity you mark legitimate regressions as wontfix? Good to know lol |
Any A workaround for the issue is using |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
If anyone comes across this issue and is just looking for some copy pasta: e.Use(middleware.LoggerWithConfig(middleware.LoggerConfig{
Format: "[${time_rfc3339}] ${status} ${method} ${path} (${remote_ip}) ${latency_human}\n",
Output: e.Logger.Output(),
})) |
Issue Description
Starting in version 4.1.7 the colors no longer show up in the middleware.Logger output for
${status}
. I suspect this is because of #1336.(Note that the output in the command line of the echo version number in my screenshots seems to have been off by one. Probably related to 09d415c.)
Checklist
Expected behaviour
Actual behaviour
Steps to reproduce
Start a webserver and go to pages with the middleware.Logger enabled. I am using this logging format:
You can easily reproduce by adding the following to the top of your
go.mod
file:then to see it broken
I should add that I am using MacOS 10.12.6 incase that makes a difference.
The text was updated successfully, but these errors were encountered: