Allow for weighting of config sources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 265
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 4
Description
Config::sources could be an ordered collection and the config sources themselves could have a weighting:
config::merge(config::Environment::with_prefix("rust")::with_weight(10));
The weight itself would be an arbitrary value, of course (and presumably the ordered collection would preserve insertion order within weighting).
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 with the Config::sources collection and the config::merge entry point named in the issue. Review how config sources are currently ordered and merged, then determine the expected behavior for arbitrary weights and insertion order within equal weights. Done means the weighting API and ordering semantics are defined and implemented with coverage for the relevant merge behavior.
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
- Mostly clear
- Newbie friendliness
- 25/100