glenux-archive/spf13--viper
1
0
Fork 0
mirror of https://github.com/spf13/viper synced 2024-11-04 20:27:02 +00:00
Code Issues Projects Releases Packages Wiki Activity

BindEnv details specified. Now less confusion.

Browse source
This commit is contained in:
Bruce Wang 2019-06-20 15:08:30 +08:00 committed by Márk Sági-Kazár
parent 2b4f7d3cde
commit 96441b4b74
1 changed files with 2 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -225,9 +225,8 @@ prefix.
`BindEnv` takes one or two parameters. The first parameter is the key name, the `BindEnv` takes one or two parameters. The first parameter is the key name, the
second is the name of the environment variable. The name of the environment second is the name of the environment variable. The name of the environment
variable is case sensitive. If the ENV variable name is not provided, then variable is case sensitive. If the ENV variable name is not provided, then
Viper will automatically assume that the key name matches the ENV variable name, Viper will automatically assume that the ENV variable is the prefix + "_" + the key name in ALL CAPS. When you explicitly provide the ENV
but the ENV variable is IN ALL CAPS. When you explicitly provide the ENV variable name which is the second parameter, it **does not** automatically add the prefix, which means if the second parameter is "id", the environment variable is just plain "ID".
variable name, it **does not** automatically add the prefix.
One important thing to recognize when working with ENV variables is that the One important thing to recognize when working with ENV variables is that the
value will be read each time it is accessed. Viper does not fix the value when value will be read each time it is accessed. Viper does not fix the value when