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

Compatibility with CLI parsing #6

Open
spacekookie opened this issue May 28, 2018 · 2 comments
Open

Compatibility with CLI parsing #6

spacekookie opened this issue May 28, 2018 · 2 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@spacekookie
Copy link
Contributor

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
@spacekookie spacekookie added enhancement New feature or request question Further information is requested labels May 28, 2018
@kamalmarhubi
Copy link

kamalmarhubi commented May 28, 2018

Similar to my comment #4 (comment), this was suggested as a non-goal in #3 (comment):

Viper looks like something that tries to do everything which is not something I think we should replicate or even try to emulate.

(Where viper has multipart configs, env vars, command line handling, and even more.)

No strong feelings, just wanted to point it out. :-)

@naturallymitchell
Copy link

I came looking for clap integration. Aside, I've so far decided not to use config crate anymore. I don't want to use toml anyway. SCL is too good, and I really haven't seen any need for the level of configurability that config offers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants