Re-thinking: Default values
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 265
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 4
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the crate's existing default-value support and the discussion in issue #323 about a config value source mechanism. Done requires a maintainer decision on whether defaults remain supported and, if so, whether they should be provided through the proposed source abstraction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100