Is there examples for extending CLI classes?

[poloka]

I have a design where I've created a RepositoryCLI class that its intent is to provide a way to checkout a GitHub repository provided a GitHub URL and a branch name. I want to allow options like:

• aliases: %w[-c --checkout-location] - to allow specifying a location for the project to be checked out to
• aliases: %w[-r --repo] - GitHub URL
• aliases: %w[-b --branch] - GitHub branch name

Now the challenge is that I have two different CLI classes that are different 'types' of repository CLIs that want the same information and then some other information. So lets say I have a SourceCLI and a DestinationCLI. I want these to be able to extend from RepositoryCLI and ask for their own options plus all the options inherited from RepositoryCLI.

What I have been doing is something like this as a Module mixin:

module RepositoryCLI
  def self.included(base)
    super(base)

    # pull in some other 'base' mixin as well
    base.class_eval do
      include BaseCLI
    end

    base.class_option :repo, aliases: %w[-r --repo], desc: REPO_DESC
    base.class_option :branch, aliases: %w[-b --branch], desc: REPO_BRANCH
    base.class_option :checkout_location, aliases: %w[-c --checkout-location], desc: CHECKOUT_LOC
  end
end

It's doable but I really wanted to know if anyone has solved this a different or more elegant way. I'm finding myself repeating this pattern even with stuff like logging level. That is what I have in my BaseCLI where I allow for the -v or --verbose for my logging on any command I run to assist in debugging my CLI commands or just to present more information to my consumer.

If anyone has an idea, let me know. I'm open to alternatives.

[poloka]

Anyone? Is there no longer support for Thor?

[poloka]

This is still unanswered. Is there is a solution for extending classes?