Logging Middleware - TagLatency doesn't have standard format between modes#1943
Conversation
|
Thanks for opening this pull request! 🎉 Please check out our contributing guidelines. If you need help or want to chat with us, join us on Discord https://gofiber.io/discord |
|
Hi there, apparently there is a problem with other modules compiling/testing on MacOs. Could anyone help? |
I don't think the problem is related this PR. Tests related timeout is falling randomly. I'll check them. |
|
Congrats on merging your first pull request! 🎉 We here at Fiber are proud of you! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord |
… format (gofiber#1943) Co-authored-by: Marcelo Gamba <gamba@itstransdata.com>
Please provide enough information so that others can review your pull request:
This change affects TagLatency in middleware logging.
Currently if you don't change the default format the latency output is using millisecond as rounding, however if you configure a custom logging message format it outputs using time.Duration (string) serialization.
I can enumerate two problems:
This PR suggests replacing time.Duration serialization to millisecond, the same used in DefaultFormat.