rubyworks / executable Goto Github PK

An undocumented feature are bang methods for parsing options. Need to revisit this and decide if it should be kept, deprecated or refined.

Currently Help output just lists option aliases as separate options. It needs to be fixed to detect aliases and attach them to the main option.

Hi,

I had an issue using your example, the shebang did not start with a / so wasn't picking up env properly. It probably should be

#!/usr/bin/env ruby

It would very cool if long option names were given automatic single letter shortcuts, as long a ashortcut hasn't already been defined.

This could be implemented in a number of ways. It could be a method or a special module to mixin that generates the aliases dynamically. Or it could just be something the option parser handles under the hood and a config option would need to be set to deactivate the feature.

Need to wrap the execute/run call procedure in a begin/rescue clause and only output one line messages by default, The $DEBUG variable could be used to let errors through the rescue clause.

Also might provide an Executable::ValidationError or something like that, and a help method to make it easier to check the validity of option values. Then again, there are probably some really good validation libraries out there that can already be integrated. So we'll see.

Including Executable into anonymous classes doesn't work b/c they have no name. Even giving them a command_name method doesn't work.