As the command line code base grows larger, how do you encapsulate your commands, options and handlers?

[VigneshwarMoorthie]

My command line project is getting bigger and I am looking for an efficient way to separate out the commands and their handlers.

My plan was to create a class that inherits the command base class to create a command.

And then create another class which implements the command handler interface.

However I delcare the option in the command class and cannot retrieve it during the GetValueForOption method call in the command handler class?

[KalleOlaviNiemitalo]

I've been deriving classes from System.CommandLine.Command and handling all the System.CommandLine specifics in those. The constructor of each such class calls SetHandler with a delegate that retrieves the argument and option values from System.CommandLine and passes them to an Invoke method in a "handler" class that does not depend on System.CommandLine at all.

[VigneshwarMoorthie]

Doesn't the Invoke method require an InvocationContext object. How are you passing the arguments and options to the Invoke method? Does your handler class implement the ICommandHandler interface?

[KalleOlaviNiemitalo]

No it doesn't implement ICommandHandler.

The delegate does something like this

ConvertCommandHandler.Invoke(
    inputFile: context.GetValueForArgument(this.inputFileArgument),
    outputFile: context.GetValueForOption(this.outputFileOption));

I don't want to spread the System.CommandLine dependencies too much in the code base while the packages are in prerelease status.