mirror of https://github.com/spf13/viper.git
docs: add section about decoding formats
Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com>
This commit is contained in:
parent
a02f9864fa
commit
030b739e60
|
@ -778,6 +778,15 @@ if err != nil {
|
||||||
|
|
||||||
Viper uses [github.com/mitchellh/mapstructure](https://github.com/mitchellh/mapstructure) under the hood for unmarshaling values which uses `mapstructure` tags by default.
|
Viper uses [github.com/mitchellh/mapstructure](https://github.com/mitchellh/mapstructure) under the hood for unmarshaling values which uses `mapstructure` tags by default.
|
||||||
|
|
||||||
|
### Decoding custom formats
|
||||||
|
|
||||||
|
A frequently requested feature for Viper is adding more value formats and decoders.
|
||||||
|
For example, parsing character (dot, comma, semicolon, etc) separated strings into slices.
|
||||||
|
|
||||||
|
This is already available in Viper using mapstructure decode hooks.
|
||||||
|
|
||||||
|
Read more about the details in [this blog post](https://sagikazarmark.hu/blog/decoding-custom-formats-with-viper/).
|
||||||
|
|
||||||
### Marshalling to string
|
### Marshalling to string
|
||||||
|
|
||||||
You may need to marshal all the settings held in viper into a string rather than write them to a file.
|
You may need to marshal all the settings held in viper into a string rather than write them to a file.
|
||||||
|
|
Loading…
Reference in New Issue