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

Re-thinking: Default values #326

Open
Tracked by #376
matthiasbeyer opened this issue Apr 23, 2022 · 1 comment
Open
Tracked by #376

Re-thinking: Default values #326

matthiasbeyer opened this issue Apr 23, 2022 · 1 comment

Comments

@matthiasbeyer
Copy link
Member

Currently we support default-values for configuration values.

Do we want to support these in the future?


Alternatives

There might be an opportunity to have default-values via some "config value source" mechanism (from #323).
The idea would be that a user might provide a "Source" object that returns their default values. This way there wouldn't be a need for default-value support from the crate.

@dnaka91
Copy link

dnaka91 commented May 1, 2022

This would be great to have as a source. Often, CLI apps work without any config due to default settings. With this as a source, we can ensure our CLI apps (or server applications and what not) work without having the user sifting through config explanations and can try out the project quickly.

@matthiasbeyer matthiasbeyer mentioned this issue Sep 17, 2022
15 tasks
@epage epage removed the re-think label Oct 23, 2024
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

3 participants