2.2. Using config files feedback
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 122
- Avg merge
- 10h 37m
- Merged PRs (30d)
- 2
Description
Going through the TODO on the page:
Evaluate crates that exist
https://docs.rs/config/latest/config/ seems to be the most popular crate.
Cli-args + multiple configs + env variables
clap has an env method/feature that allows setting an environment variable to read from if the CLI argument isn't present
To throw in configuration files, there's an open issue: https://github.com/clap-rs/clap/issues/748 There are also various (less popular) crates that integrate with clap by third-party authors.
Can configure do all this? Is there a nice wrapper around it?
configure hasn't had a release in 5 years. I don't think it's relevant anymore.
Contributor guide
No contributing guide indexed for this repository
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
Locate the book page containing the cited configuration TODO and read its surrounding guidance. Review the linked config, clap, and configure resources, then update the page to reflect the current findings and verify that the TODO is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100