As of right now, only logs at the level error are logged. Therefore, users don't see any of these warnings anyway (by default).
I suppose that if someone is familiar with logging enough to choose a custom logging level (e.g. by setting RUST_LOG), they would find logging a purely informational thing (server started, it's serving on that port) as a warning confusing.
But maybe it's just me :)
So, the proposed plan is: print info or higher logs by default. Use info when it's actually an informational log.
As of right now, only logs at the level
errorare logged. Therefore, users don't see any of these warnings anyway (by default).I suppose that if someone is familiar with logging enough to choose a custom logging level (e.g. by setting
RUST_LOG), they would find logging a purely informational thing (server started, it's serving on that port) as a warning confusing.But maybe it's just me :)
So, the proposed plan is: print
infoor higher logs by default. Useinfowhen it's actually an informational log.I expressed my thoughts on logging in https://github.com/GothenburgBitFactory/taskchampion-sync-server/issues/27#issuecomment-2241359103. If we can agree on what the logging should look like in this project, I'm happy to send a few small PRs.