-
Notifications
You must be signed in to change notification settings - Fork 293
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
Has the approach to verbs in v2 changed? #500
Comments
Two things:
|
Cool So i just tried build 2.1.1-beta and I cannot get the snippet above to compile
|
Did it mention a file/line number? |
Its in my simple test app and when I look at the object explorer I only see a ParseArguments and not other overloads for more generic args. |
Sorry I misread and thought you were building the source code of the library. This worked for me on the latest beta: var result = CommandLine.Parser.Default.ParseArguments<AddOptions, UpdateOptions, DeleteOptions(args).MapResult(
(AddOptions aopts) => {return ""; },
(UpdateOptions upopts) => {return ""; },
(DeleteOptions dopts) => {return ""; },
(IEnumerable<Error> errs) => {return ""; }); |
That helped -- I found the issue :) It appears you must add the using statement
Without that it doesn't find the extension methods or the Error option. |
I was reviewing the code and the following wiki for vers
https://github.com/gsscoder/commandline/wiki/Latest-Version and I cannot see how they line up.
Ex - the following will not compile
It complains that there is no support for more than one Generic and from looking at the code, I didn't see any overrides or extensions to ParseArguments that supports multiple generics. So I was curious if the approach had changed.
The text was updated successfully, but these errors were encountered: