No mechanism to override logger

[idcmp]

Preflight Checklist

• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description

v.logger is now an interface, which is great, but there's no mechanism to override the default jwwLogger{} for the global Viper (GetViper()).

Proposed Solution

introduce a GetViper().UseLogger(newLogger Logger) ?

Alternatives Considered

No response

Additional Information

No response

[github-actions]

👋 Thanks for reporting!

A maintainer will take a look at your issue shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️

[sagikazarmark]

Thanks for opening this issue @idcmp !

I opened another issue to track this as well: #1270

[sagikazarmark]

#1275 adds an experimental WithLogger function that allows overriding the builtin logger. Please note that it is not covered by the backwards compatibility promise.