Skip to content
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

Quick Guide is missing #90

Open
nikosT opened this issue May 15, 2020 · 3 comments
Open

Quick Guide is missing #90

nikosT opened this issue May 15, 2020 · 3 comments

Comments

@nikosT
Copy link

nikosT commented May 15, 2020

The documentation for quick use is not straight forward. Someone will need a lot of time to understand how this library works.

@miikama
Copy link

miikama commented Jun 28, 2020

For me the most non-obvious thing was that one has to have a config_default.yaml inside your own library. Maybe this could be highlighted a bit more clearly in the documentation.

As a side note, I'd really prefer giving the name/file_path of the configuration file template as an argument to the confuse.Configuration()

@BrenBarn
Copy link

BrenBarn commented Aug 21, 2020

The documentation is indeed somewhat lacking, both in terms of quickstart and more detail on the API. For instance, the example under "your application directory" makes use of a variable called confuse.CONFIG_FILENAME, but this variable is not documented anywhere.

Also, there is no explicit description in the documentation of how confuse maps configuration keys onto YAML files, or what the filenames of the config files are, etc. This makes it difficult to get started because the documentation only describes how to read existing configuration files, but not how to create them.

There are all manner of issues that were resolved by telling people to use .set_file or various things in confuse.util, none of which are documented. The readme says that the documentation describes the API "in detail" but it is quite far from doing this.

@sampsyo
Copy link
Member

sampsyo commented Aug 22, 2020

Quite true! We would love help getting that documentation started if anyone has time to open a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants