FREQ: a #skip_subcommand_parsing method to allow options but arbitrary parameters about cri

[denisdefreyne]

At the moment, Cri commands either accept subcommands, or accept arguments (an arbitrary number of them).

Do you need to have a command that can take both? (I imagine that could get confusing.)

[RoUS]

My use-case is a command configure with known subcommands (user, system, etc.). It's the subcommands that need to take arbitrary arguments -- otherwise I end up with something ugly like

configure user --option=foo --value=bar
configure user --option=format --value-yaml

as opposed to something like

configure user foo=bar format=yaml

This is oversimplified and somewhat contrived, but I hope it gets my idea across.

[denisdefreyne]

@RoUS Would something along these lines work?

# frozen_string_literal: true

require 'cri'

config = {
  'animal' => 'cat',
  'sound' => 'meow',
}

config_cmd = Cri::Command.define do
  name        'conf'
  usage       'conf [subcommand] …'
  summary     'manage configuration'
  description '…'
end

set_cmd = Cri::Command.define do
  name        'set'
  usage       'set key=value ...'
  summary     'set config values'
  description '…'

  run do |opts, args|
    args.each do |string|
      key, value = string.split('=')
      config[key] = value
    end
  end
end

unset_cmd = Cri::Command.define do
  name        'unset'
  usage       'unset key ...'
  summary     'unset config values'
  description '…'

  run do |opts, args|
    args.each do |key|
      config.delete(key)
    end
  end
end

config_cmd.add_command(set_cmd)
config_cmd.add_command(unset_cmd)

config_cmd.run(ARGV)

pp config

% ruby conf.rb unset animal
{"sound"=>"meow"}
% ruby conf.rb unset asdf
{"animal"=>"cat", "sound"=>"meow"}
% ruby conf.rb set fn=Denis ln=Defreyne
{"animal"=>"cat", "sound"=>"meow", "fn"=>"Denis", "ln"=>"Defreyne"}

[RoUS]

Yes, I think that would do it; I totally missed the concept of using #run in the command definition. Thanks!

[denisdefreyne]

Cool! I’ll close this issue now.