Replies: 2 comments 6 replies
-
One thing that might help is
This should limit the configuration parsing to the specific section and ignore everything outside of it. I know I use this for parsing when the options are part of a much bigger configuration file. |
Beta Was this translation helpful? Give feedback.
6 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am trying a use CLI11 configuration file where I do not know which options are available. A kind a pass through to another lib.
For example:
Here, I got a "kafka" command, that accept topic as an option (a fairly common one for kafka),
and I try to add an "options" subcommand that will accept any options (A, B, C, ...) with its associated values.
What will be the best way to acheive this (if possible), without using "options" becoming an option mapped to vector of string and keep the .ini format for this subcommand.
So not like this
So far, I have tried options subcommand with nameless option without any success (like all my previous attempt, allow extra flag, ...).
Latest experimentation, with drawbacks (allow config extra in app is not wanted but only at options subcommand level).
I do not see the value in the remaining loop.
Beta Was this translation helpful? Give feedback.
All reactions