Skip to content

docs: update supported formats list for v1.20 changes #2102

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.

Sign up for GitHub

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

Open
ismaildasci wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −2
Open

docs: update supported formats list for v1.20 changes #2102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,9 +90,11 @@ Viper requires minimal configuration to load config files. Viper currently suppo
* JSON
* TOML
* YAML
* INI
* envfile
* Java Propeties

> **Note:** Since v1.20, INI, HCL and Java Properties formats are no longer included in core Viper.
> You can still use them by importing from [github.com/go-viper/encoding](https://github.com/go-viper/encoding).
> See the [upgrade guide](UPGRADE.md#breaking-hcl-java-properties-ini-removed-from-core) for details.

A single Viper instance only supports a single configuration file, but multiple
paths may be searched for one.
Expand Down