Eirik Tsarpalis
Eirik Tsarpalis
I can't think of a good way to surface those environment variable names automagically in a way that works for everyone. For the sake of DRY you could perhaps use...
You can use the [`GetResults`](https://github.com/fsprojects/Argu/blob/2231fa039755316e73234f5fde3539dbf23a85ce/src/Argu/ParseResults.fs#L70-70) method which returns a list of all arguments. So if you pass the args ``` -f 1 -f 2 -f 3 ``` Then `GetResults `...
Sounds reasonable. It's been ages since I wrote that code, but I have a slight hunch that the restriction might have been motivated by technical reasons.
Probably not, at least it hasn't been addressed intentionally.
I don't believe this is possible, currently.
Sure, I can't think of a good way to encode positional arguments. Proposals/PRs are welcome.
I'm not sure I understand what the expected behaviour is. The method prints literal quotes but fails to do so if you add newline chars?
> PrintCommandLineArgumentsFlat must quote parameters with newline chars, like whitespaces. Could you elaborate why? Why shouldn't it be quoted if that is not the case?
The `MainCommand` and `First` attributes are generally contradictory. It seems like this combination should be raising an error.
> Is there an ideal way of including a key/value input that would allow the user to provide the keys? Basically Dictionary / (string * string) list but that's unsupported...