Preflight Checklist
- [X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
Problem Description
I want to control the detailed behavior of specific encoder or decoder, or add new encoder/decoder. Without exposing these two fields, I can't do that.
For example:
If we use properties format and want to give a customized match rule when replacing the inner content of ${}. We can't do that, because properties handles it and do the replacement before the application can handle it. Without exposing the codec registry fields, we can not turn off DisableExpansion in Properties.
Proposed Solution
expose encoderRegistry and decoderRegistry in Viper
Alternatives Considered
No response
Additional Information
No response
Comment From: github-actions[bot]
👋 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! ❤️
Comment From: github-actions[bot]
Issues with no activity for 30 days are marked stale and subject to being closed.