Document complex object binding

[cmeyertons]

I've been creating all of my handlers according to the documentation like this:

command.Handler = CommandHandler.Create((IEnumerable<string> include, int count) =>
            {
                var request = new SchemaRollbackRequest(include, count);

                var svc = Container.ResolveService<ISchemaService>();

                svc.RollbackSchema(request);
            });

and it's a huge pain to update the args for every new option (requires multiple updates).

i just started creating a new command that required more than 7 options and stumbled across #458 where it's discussed to bind to a complex object, which fits my use case perfectly.

can documentation be added around the complex object binding?

[jonsequitur]

Though it's not proper documentation, the interactive tutorial covers this to some extent: https://github.com/dotnet/command-line-api#interactive-tutorials

[dashesy]

I am not sure how that tutorial is related to creating a complex object from more than 7 options. Is there a way to parse more than 7 options using concepts like Option and TryConvertArgument?

As soon as the lamda has more than 7 options we get this:

Cannot convert lambda expression to type 'Delegate' because it is not a delegate type.

---

Actually, I found this and this example. So binding is by name.

[lucjanl]

+1

This feature is a bit "hidden" and the code isn't enough documented. Personally I struggled several hours to find out how to do it before I found the #458