-
Notifications
You must be signed in to change notification settings - Fork 2k
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My opinion #1059
Comments
👋 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, https://twitter.com/sagikazarmark/status/1306904078967074816 Thank you! ❤️ |
@yqcs case insensitivity is necessary for merging configuration from various sources (for example env vars are usually upper case). You can track #1014 for this issue. As for comments: that's an unfortunate consequence of writing config. Actually, the config write feature is not supposed to be used for saving config state. It's useful for features like writing default config. I'm closing the issue as it's not actually an enhancement or not new. |
Why change capital letters to lowercase letters without permission? Comments are also automatically cleared. I think these should be set manually.
The text was updated successfully, but these errors were encountered: