-
Notifications
You must be signed in to change notification settings - Fork 109
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
How different it is from spf13/viper? #53
Comments
There is a huge difference in the ideas behind both. Viper is a kinda Swiss knife for configuration - it handles a huge variety of use cases and it is massive, and many things are magically happening. This library is about simplicity and explicitness, so there is no magic, maybe a bit more code and fewer features, but it keeps things simple: read config from Another feature that I proud the most of - is environment variable documentation, i.e. the library can prompt the list of all environment variables and their descriptions into help output. After my own production experience, having env. variables silently (without having a detailed description of them somewhere) is a real headache in long-running projects. So the library follows "documentation as a code" principle and allows you to just describe env. variable once (in structure tags) and then use in to read docs and to have an up-to-date description in help. Hope this will help you to understand the difference and know when to use each library. |
Cool thank you, this answers it. Great work making it. |
I was going to use viper and then stumbled on this... Want to understand the differences to make a choice.
The text was updated successfully, but these errors were encountered: