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.

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

Jump to bottom

unchecked does not support optional values #19

Open
pltb opened this issue Oct 2, 2017 · 1 comment
Open

unchecked does not support optional values #19

pltb opened this issue Oct 2, 2017 · 1 comment

Comments

@pltb
Copy link

pltb commented Oct 2, 2017

No description provided.

@carlpulley
Copy link
Owner

This is by design. I've taken the road where I assume that all configuration paths/keys must have defined values (i.e. no path/key can be left undefined).

Doing this allows one to know when something has been intentionally set and when something has been accidentally left undefined.

As this is by design, I plan to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@carlpulley @pltb