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

document why default values are always strings #10

Open
willkg opened this issue Aug 12, 2016 · 2 comments
Open

document why default values are always strings #10

willkg opened this issue Aug 12, 2016 · 2 comments

Comments

@willkg
Copy link
Owner

willkg commented Aug 12, 2016

There are a couple of architecture choices that we've made that should get documented so it's clear why it is the way it is.

One that comes up in conversations with people is that default values are always strings that get passed to the parser rather than parsed values. For example 'true' vs. True. I think it's a worthwhile thing to explain in the docs. One nice thing that might come of this is that someone comes up with a better way to meet my requirements.

This issue covers writing that up.

@willkg willkg added this to the 1.0 milestone Dec 21, 2018
@willkg willkg removed this from the 1.0 milestone Jan 7, 2019
@pjz
Copy link
Contributor

pjz commented Aug 21, 2019

I think https://github.com/willkg/everett/blob/master/everett/manager.py#L874 is enough to let this be closed.

@willkg
Copy link
Owner Author

willkg commented Aug 26, 2019

That's buried in the ConfigManager API docs and this issue covers writing something that's easier for everyone to bump into who needs to.

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

No branches or pull requests

2 participants