Compatibility with CLI parsing

Open
#6 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

Start by reviewing the compatibility questions around the config crate, clap.rs, structopt, and thunder. Determine the intended behavior when CLI options override configuration values and what a generic integration would need to support; done should include a decided compatibility scope and an agreed implementation path.

Written by the indexing model from the issue text.

Description

enhancement question

The general idea behind this feature is the following. Take a configuration file:

my_option = "foo"

and a CLI which also wants to provide the option my_option which, if provided overrides the config state and if isn't, just uses the default provided by the configuration.

Open Questions
  • A similar problem was already solved by config (and others), can we just use their work/ be compatible with them?
  • It should also be to use this feature with clap.rs directly, structopt or thunder so a more generic approach is generally good
Dominant language
Rust
Stars
1k
Forks
78
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-cli/confy

All issues in rust-cli/confy

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.