We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be nice if a config file does not need an extension. It's not uncommon for a dot file to not have an extension, but be in a metadata format.
In order to solve how to parse the file would be ideal to use viper.SetConfigType().
viper.SetConfigType()
Example:
Reading in a config file $HOME/.config that is YAML formatted.
$HOME/.config
viper.AddConfigPath(homeDir) viper.SetConfigType("yaml") viper.SetConfigName(".config")
The text was updated successfully, but these errors were encountered:
Any update on this, We are waiting for this feature too!
Sorry, something went wrong.
+1 !
We're waiting for this too.
This has been implemented in #722
No branches or pull requests
It would be nice if a config file does not need an extension. It's not uncommon for a dot file to not have an extension, but be in a metadata format.
In order to solve how to parse the file would be ideal to use
viper.SetConfigType()
.Example:
Reading in a config file
$HOME/.config
that is YAML formatted.The text was updated successfully, but these errors were encountered: