MooseX-Types 0.22
Kwalitee Issues
This is not the latest release. The following issues may have already been fixed in the newer releases.
No Core Issues.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Modules
Name | Abstract | Version | View |
---|---|---|---|
MooseX::Types | Organise your Moose types in libraries | 0.22 | metacpan |
MooseX::Types::Base | Type library base class | 0.22 | metacpan |
MooseX::Types::CheckedUtilExports | Wrap L<Moose::Util::TypeConstraints> to be safer for L<MooseX::Types> | 0.22 | metacpan |
MooseX::Types::Combine | Combine type libraries for exporting | 0.22 | metacpan |
MooseX::Types::Moose | Types shipped with L<Moose> | 0.22 | metacpan |
MooseX::Types::TypeDecorator | More flexible access to a Type Constraint | 0.22 | metacpan |
MooseX::Types::UndefinedType | Represents a not yet defined type | 0.22 | metacpan |
MooseX::Types::Util | Common utility functions for the module | 0.22 | metacpan |
MooseX::Types::Wrapper | Wrap exports from a library | 0.22 | metacpan |