What’s the bar for breaking compatibility? There’s some precedent for doing so when it prevents confusion:
feat(logger): return primary level as is, without conversion
This is breaking change, but inevitable to not confuse users.
Changing the default log level to something safer for production doesn’t seem like a huge stretch by comparison.
It would be nice to have a deprecation path. Can Logger reliably distinguish between an explicitly configured log level and falling back to its implicit :debug default? If so, it seems like reliance on the implicit default could first be deprecated, giving users who actually want :debug a chance to configure it explicitly.
Another interesting data point: Phoenix’s default production configuration sets the level to :info. If Phoenix is as widely used as I think it is, I suspect this masks the problem since most people never have to deal with the consequences of Logger’s defaults.
