MooseX::Getopt::Defanged::Exception::Generic - Something went wrong with MooseX::Getopt::Defanged, most likely a bug in the code using it. River stage zero No dependents

Something happened while talking to Getopt::Long. Usually this means there is a bug in the code using MooseX::Getopt::Defanged....

ELLIOTJS/MooseX-Getopt-Defanged-v1.18.0 - 08 Sep 2010 22:19:24 GMT

MooseX::Getopt::Defanged::Exception::InvalidSpecification - An invalid option specification was given to MooseX::Getopt::Defanged. River stage zero No dependents

An invalid option specification or unknown standard option was given to MooseX::Getopt::Defanged. Basically, this means there is a bug in the code....

ELLIOTJS/MooseX-Getopt-Defanged-v1.18.0 - 08 Sep 2010 22:19:24 GMT

MooseX::Runnable::Invocation::Scheme::MooseX::Getopt - run MX::Getopt classes River stage one • 2 direct dependents • 2 total dependents

This role will be used by "MooseX::Runnable::Invocation" to create an instance of the class to be run with "MooseX::Getopt". Any args not consumed by MX::Getopt will be passed to the class's run method. (See the test "t/basic-mx-getopt.t" for an exam...

ETHER/MooseX-Runnable-0.10 - 13 Mar 2016 00:42:15 GMT

MooseX::Getopt::Meta::Attribute::Trait::NoGetopt - Optional meta attribute trait for ignoring parameters River stage four • 122 direct dependents • 1036 total dependents

This is a custom attribute metaclass trait which can be used to specify that a specific attribute should not be processed by "MooseX::Getopt". All you need to do is specify the "NoGetopt" metaclass trait. has 'foo' => (traits => [ 'NoGetopt', ... ], ...

ETHER/MooseX-Getopt-0.74 - 23 Sep 2018 23:42:11 GMT

MooseX::App::Cmd - Mashes up MooseX::Getopt and App::Cmd River stage two • 30 direct dependents • 47 total dependents

This module marries App::Cmd with MooseX::Getopt. Use it like App::Cmd advises (especially see App::Cmd::Tutorial), swapping App::Cmd::Command for MooseX::App::Cmd::Command. Then you can write your moose commands as Moose classes, with MooseX::Getopt...

ETHER/MooseX-App-Cmd-0.32 - 12 Sep 2015 01:11:17 GMT

MooseX::App - Write user-friendly command line apps with even less suffering River stage two • 36 direct dependents • 61 total dependents

MooseX-App is a highly customisable helper to write user-friendly command line applications without having to worry about most of the annoying things usually involved. Just take any existing Moose class, add a single line ("use MooseX-App qw(PluginA ...

MAROS/MooseX-App-1.41 - 13 May 2019 20:55:25 GMT

MooseX::Runnable - Tag a class as a runnable application River stage one • 2 direct dependents • 2 total dependents

MooseX::Runnable is a framework for making classes runnable applications. This role doesn't do anything other than tell the rest of the framework that your class is a runnable application that has a "run" method which accepts arguments and returns th...

ETHER/MooseX-Runnable-0.10 - 13 Mar 2016 00:42:15 GMT

MooseX::Daemonize - Role for daemonizing your Moose based application River stage two • 11 direct dependents • 19 total dependents

Often you want to write a persistent daemon that has a pid file, and responds appropriately to Signals. This module provides a set of basic roles as an infrastructure to do that....

ETHER/MooseX-Daemonize-0.22 - 07 Dec 2019 01:26:55 GMT

MooseX::Role::DBIC - make your Moose class encapsulate one or more DBIC schemas River stage zero No dependents

Generic parameterized Moose role to give your class accessors for managing one or more DBIx::Class::Schema objects. Can be composed with MooseX::Role::DBIx::Connector to share the same dsn, user, password, and connection attributes....

RBUELS/MooseX-Role-DBIC-0.01 - 07 Apr 2011 23:58:13 GMT

MooseX::LogDispatch - A Logging Role for Moose River stage two • 10 direct dependents • 14 total dependents

Log::Dispatch role for use with your Moose classes....

JGOULAH/MooseX-LogDispatch-1.2002 - 18 Apr 2010 19:01:12 GMT

MooseX::App::Simple - Single command applications River stage two • 36 direct dependents • 61 total dependents

MooseX-App-Simple works basically just as MooseX::App, however it does not search for commands and assumes that you have all options and parameters defined in the current class. Read the Tutorial for getting started with a simple MooseX::App command ...

MAROS/MooseX-App-1.41 - 13 May 2019 20:55:25 GMT

MooseX::SimpleConfig - A Moose role for setting attributes from a simple configuration file River stage two • 27 direct dependents • 80 total dependents

This role loads simple files to set object attributes. It is based on the abstract role MooseX::ConfigFromFile, and uses Config::Any to load your configuration file. Config::Any will in turn support any of a variety of different config formats, detec...

ETHER/MooseX-SimpleConfig-0.11 - 16 Nov 2014 22:05:07 GMT

MooseX::ConfigFromFile - An abstract Moose role for setting attributes from a configfile River stage three • 12 direct dependents • 102 total dependents

This is an abstract role which provides an alternate constructor for creating objects using parameters passed in from a configuration file. The actual implementation of reading the configuration file is left to concrete sub-roles. It declares an attr...

ETHER/MooseX-ConfigFromFile-0.14 - 16 Aug 2015 03:13:38 GMT

MooseX::App::Cmd::Command - Base class for MooseX::Getopt based App::Cmd::Commands River stage two • 30 direct dependents • 47 total dependents

This is a replacement base class for App::Cmd::Command classes that includes MooseX::Getopt and the glue to combine the two....

ETHER/MooseX-App-Cmd-0.32 - 12 Sep 2015 01:11:17 GMT

MooseX::LazyLogDispatch - A Logging Role for Moose River stage zero No dependents

Log::Dispatch role for use with your Moose classes....

BLBLACK/MooseX-LazyLogDispatch-0.02 - 21 Dec 2007 18:14:28 GMT

MooseX::AttributeCloner River stage zero No dependents

The purpose of this Role is to take all the attributes which have values in the current class, and populate them directly into a new class object. The purpose of which is that if you have data inputted on the command line that needs to propagate thro...

SETITESUK/MooseX-AttributeCloner-0.27 - 25 Jan 2013 10:22:14 GMT

MooseX::Types::Path::Class - A Path::Class type library for Moose River stage three • 123 direct dependents • 532 total dependents

MooseX::Types::Path::Class creates common Moose types, coercions and option specifications useful for dealing with Path::Class objects as Moose attributes. Coercions (see Moose::Util::TypeConstraints) are made from both "Str" and "ArrayRef" to both P...

ETHER/MooseX-Types-Path-Class-0.09 - 08 Jun 2016 01:06:03 GMT

MooseX::Attribute::Prototype - Borrow and Extend Moose Attrtibutes River stage zero No dependents

This module implements attribute prototyping -- the practice of borrowing an attribute from a role and optionally overriding/extending the attribute definition. This is This works very similar to Moose's native attribute cloning, but allows for addit...

CTBROWN/MooseX-Attribute-Prototype-0.10 - 19 Jul 2009 11:55:47 GMT

MooseX::Daemonize::Pid::File - PID file management for MooseX::Daemonize River stage two • 11 direct dependents • 19 total dependents

This object extends MooseX::Daemonize::Pid to add persistence in a Pidfile. This class sets up some basic coercion routines for itself so that it can be created from a *Str* (a file name), *ArrayRef* (an array of path components for a filename) or a ...

ETHER/MooseX-Daemonize-0.22 - 07 Dec 2019 01:26:55 GMT

MooseX::Role::DBIx::Connector - give your Moose class DBIx::Connector powers River stage zero No dependents

Generic parameterized Moose role to give your class accessors to manage one or more DBIx::Connector connections....

RBUELS/MooseX-Role-DBIx-Connector-0.11 - 12 Mar 2010 20:18:42 GMT

48 results (0.046 seconds)