NAME

SYNOPSIS

  package MyApp;
  use MooseX::App qw(Color);
 
  option 'global_option' => (
      is            => 'rw',
      isa           => 'Bool',
      documentation => q[Enable this to do fancy stuff],
  ); # Global option
  
  has 'private' => (
      is              => 'rw',
  ); # not exposed

Write multiple command classes (If you have only a single command class you should use MooseX::App::Simple instead). Packackes in the namespace may be deeply nested.

  package MyApp::SomeCommand;
  use MooseX::App::Command; # important (also imports Moose)
  extends qw(MyApp); # optional, only if you want to use global options from base class
  
  # Positional parameter
  parameter 'some_parameter' => (
      is            => 'rw',
      isa           => 'Str',
      required      => 1,
      documentation => q[Some parameter that you need to supply],
  );
  
  option 'some_option' => (
      is            => 'rw',
      isa           => 'Int',
      required      => 1,
      documentation => q[Very important option!],
  ); # Option
  
  sub run {
      my ($self) = @_;
      # Do something
  }

And then you need a simple wrapper script (called eg. myapp):

 #!/usr/bin/env perl
 use MyApp;
 MyApp->new_with_command->run;

On the command line:

 bash$ myapp help
 usage:
     myapp <command> [long options...]
     myapp help
 
 global options:
     --global_option    Enable this to do fancy stuff [Flag]
     --help --usage -?  Prints this usage information. [Flag]
 
 available commands:
     some_command    Description of some command
     another_command Description of another command
     help            Prints this usage information

or

 bash$ myapp some_command --help
 usage:
     myapp some_command <SOME_PARAMETER> [long options...]
     myapp help
     myapp some_command --help
 
 parameters:
     some_parameter     Some parameter that you need to supply [Required]
 
 options:
     --global_option    Enable this to do fancy stuff [Flag]
     --some_option      Very important option! [Int,Required]
     --help --usage -?  Prints this usage information. [Flag]

DESCRIPTION

MooseX-App will then

• Find, load and initialise the command classes (see MooseX::App::Simple for single class/command applications)
• Create automated help and documentation from modules POD as well as attributes metadata and type constraints
• Read, encode and validate the command line options and positional parameters entered by the user from @ARGV and %ENV (and possibly prompt the user for additional parameters see MooseX::App::Plugin::Term)
• Provide helpful error messages if user input cannot be validated (either missing or wrong attributes or Moose type constraints not satisfied) or if the user requests help.

Commandline options are defined using the 'option' keyword which accepts the same attributes as Moose' 'has' keyword.

  option 'some_option' => (
      is            => 'rw',
      isa           => 'Str',
  );

This is equivalent to

  has 'some_option' => (
      is            => 'rw',
      isa           => 'Str',
      traits        => ['AppOption'],   # Load extra metaclass
      cmd_type      => 'option',        # Set attribute type
  );

Single letter options are treated as flags and may be combined with each other. However such options must have a Boolean type constraint.

 option 'verbose' => (
      is            => 'rw',
      isa           => 'Bool',
      cmd_flag      => 'v',
  );

Positional parameters are defined with the 'parameter' keyword

  parameter 'some_option' => (
      is            => 'rw',
      isa           => 'Str',
  );

This is equivalent to

  has 'some_option' => (
      is            => 'rw',
      isa           => 'Str',
      traits        => ['AppOption'],
      cmd_type      => 'parameter',
  );

All keywords are imported by Moosex::App (in the app base class) and MooseX::App::Command (in the command class) or MooseX::App::Simple (single class application).

Furthermore, all options and parameters can also be supplied via %ENV

  option 'some_option' => (
      is            => 'rw',
      isa           => 'Str',
      cmd_env       => 'SOME_OPTION', # sets the env key
  );

Moose type constraints help MooseX::App to construct helpful error messages and parse @ARGV in a meaningful way. The following type constraints are supported:

• ArrayRef: Specify multiple values ('--opt value1 --opt value2', also see app_permute and cmd_split)
• HashRef: Specify multiple key value pairs ('--opt key=value --opt key2=value2', also see app_permute)
• Enum: Display all possibilities
• Bool: Flags that do not require values
• Int, Num: Used for proper error messages

Read the Tutorial for getting started with a simple MooseX::App command line application.

METHODS

 my $myapp_command = MyApp->new_with_command();

 my $obj = MyApp->new_with_command(%default);

 my $obj = MyApp->new_with_command( ARGV => \@myARGV );

 my $obj = MyApp->initialize_command_class($command_name,%default);

GLOBAL OPTIONS

 app_base 'my_script'; # Defaults to $0

 app_fuzzy 1; # default
 OR
 app_fuzzy 0;

 app_strict 0; # default
 OR
 app_strict 1;

 app_prefer_commandline 0; # default
 or
 app_prefer_commandline 1;

 app_namespace 'MyApp::Commands', 'YourApp::MoreCommands';
 OR
 app_namespace();

 app_exclude 'MyApp::Commands::Roles','MyApp::Commands::Utils';

 app_command_name {
     my ($package_short,$package_full) = @_;
     # munge package name;
     return $command_name;
 };

 app_command_register
    do      => 'MyApp::Commands::DoSomething',
    undo    => 'MyApp::Commands::UndoSomething';

 app_description qq[Description text];

 app_usage qq[myapp --option ...];

 app_permute 0; # default
 OR
 app_permute 1;

GLOBAL ATTRIBUTES

ATTRIBUTE OPTIONS

• cmd_tags - Extra tags (as used by the help)
• cmd_flag - Override option/parameter name
• cmd_aliases - Additional option/parameter name aliases
• cmd_split - Split values into ArrayRefs on this token or RegEx
• cmd_position - Specify option/parameter order in help
• cmd_env - Read options/parameters from %ENV
• cmd_count - Value of option equals to number of occurrences in @ARGV
• cmd_negate - Adds an option to negate boolean flags

Refer to MooseX::App::Meta::Role::Attribute::Option for detailed documentation.

METADATA

• Package names
• required options for Moose attributes
• documentation options for Moose attributes
• Moose type constraints (Bool, ArrayRef, HashRef, Int, Num, and Enum)
• Documentation set via app_description, app_usage, command_short_description, command_long_description and command_usage
• POD (NAME, ABSTRACT, DESCRIPTION, USAGE, SYNOPSIS, OVERVIEW, COPYRIGHT, LICENSE, COPYRIGHT AND LICENSE, AUTHOR and AUTHORS sections)
• Dist::Zilla ABSTRACT tag if no POD is available yet

PLUGINS

 use MooseX::App qw(PluginA PluginB);

Currently the following plugins are shipped with MooseX::App

• MooseX::App::Plugin::BashCompletion

  Adds a command that generates a bash completion script for your application. See third party MooseX::App::Plugin::ZshCompletion for Z shell completion.

• MooseX::App::Plugin::Color

  Colorful output for your MooseX::App applications.

• MooseX::App::Plugin::Config

  Config files for MooseX::App applications.

• MooseX::App::Plugin::ConfigHome

  Try to find config files in users home directory.

• MooseX::App::Plugin::Term

  Prompt user for options and parameters that were not provided via options or params. Prompt offers basic editing capabilities and non-persistent history.

• MooseX::App::Plugin::Typo

  Handle typos in command names and provide suggestions.

• MooseX::App::Plugin::Version

  Adds a command to display the version and license of your application.

• MooseX::App::Plugin::Man

  Display full manpage of application and commands.

• MooseX::App::Plugin::MutexGroup

  Allow for mutally exclusive options.

• MooseX::App::Plugin::Depends

  Adds dependent options.

Refer to Writing MooseX-App Plugins for documentation on how to create your own plugins.

DEVELOPMENT

CAVEATS & KNOWN BUGS

In some cases - especially when using non-standard class inheritance - you may end up with command classes lacking the help attribute. In this case you need to include the following line in your base class or command classes.

 with qw(MooseX::App::Role::Common);

When manually registering command classes (eg. via app_command_register) in multiple base classes with different sets of plugins (why would you ever want to do that?), then meta attributes may lack some attribute metaclasses. In this case you need to load the missing attribute traits explicitly:

 option 'argument' => (
    depends => 'otherargument',
    trait   => ['MooseX::App::Plugin::Depends::Meta::Attribute'], # load trait
 );

SEE ALSO

For alternatives you can check out

MooseX::App::Cmd, MooseX::Getopt, MooX::Options, MooX::Cmd and App::Cmd

SUPPORT

AUTHOR

    Maroš Kollár
    CPAN ID: MAROS
    maros [at] k-1.com
    
    http://www.k-1.com

CONTRIBUTORS

In no particular order: Andrew Jones, George Hartzell, Steve Nolte, Michael G, Thomas Klausner, Yanick Champoux, Edward Baudrez, David Golden, J.R. Mash, Thilo Fester, Gregor Herrmann, Sergey Romanov, Sawyer X, Roman F., Hunter McMillen, Maik Hentsche, Alexander Stoddard, Marc Logghe, Tina Müller, Lisa Hare, Jose Luis Martinez, Frank Schreiner

You are more than welcome to contribute to MooseX-App. Please have a look at the <https://github.com/maros/MooseX-App/issues?q=is%3Aissue+is%3Aopen+label%3AWishlist> list of open wishlist issues for ideas.

COPYRIGHT

This library is free software and may be distributed under the same terms as perl itself. The full text of the licence can be found in the LICENCE file included with this module.