I’m struggling to express it clearly… in my head, ...

# clikt

[Rob Elliot]

I’m struggling to express it clearly… in my head, the commands functionality is a layer of added functionality on top of the basic parsing. So it feels back to front to have a super class CliktCommand with things about commands and subcommands in it, and then override it with NoOpCommand to not use that, rather than to have a type focussed solely on the parsing of options, and then augment it with one that knows about commands. Does that make any sort of sense?

It’s mostly a matter of learning - if CliktCommand had extended Parser, such that my parser could also extend Parser, I’d probably have cottoned on to how to get to what I wanted earlier.

I appreciate I’m not using the lib as you primarily expect people to, so it’s just a suggestion.