Undocumented change in 2.6 seems to prevent multiple keys for same flag pointing to default value

[smackesey]

I have a command declared like this:

desc 'Compute a matrix and save to the desktop'
arg_name 'matrix'
command :compute do |c|

  c.desc 'format'
  c.default_value 'csv'
  c.flag :f, :format

  c.desc 'path to file'
  c.default_value File.join(conf.compute_output_dir, "#{Time.now.strftime("%y%m%d%H%M%S")}")
  c.flag :p, :path

  c.action(&method(:compute))
end

In 2.5.6, inside the called method compute, the options hash would contain pairs of entries for both :f and :format and :p and :path that pointed to the default values. In 2.6, the long form of the option is not being included in the Hash-- it has only :f and :p keys. If I switch the order of the symbols in the flag list, then it is only :format and :path that show up-- so it looks like only the first name for the flag is recorded. This is happening either with or without the subcommand_option_handling :normal directive introduced in 2.6.

[shantipants]

I've run into the same issue. fc56475 Seems to be a likely culprit, but I don't really have time to dig into it. Hope this helps!

[mckern]

+1

[davetron5000]

Yeah, this is subtle. Since I moved to OptionParser, I just had the block of on set the value in the hashes for all aliases in symbol and string form. The defaults aren't set that way. Looking into it…

[davetron5000]

Once Travis verifies the build is working, I'll release 2.6.1 and post about it here. Sorry for the regression!

Does anyone on this issue have open source apps using GLI? I could definitely use a larger testbed…

[davetron5000]

2.6.1 is on RubyGems - please re-open if it didn't fix it and sorry again.