Kwalitee Issues

use_strict

Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.

Error: MOP4Import::Base::Configure

proper_libs

Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.

Error: Base/CLI.pm, Base/Configure.pm, Declare.pm, FieldSpec.pm, Opts.pm, PSGIEnv.pm, Types.pm, Util.pm, Util/FindMethods.pm

use_warnings

Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: MOP4Import::Base::Configure, MOP4Import::PSGIEnv

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
MOP4Import::Base::CLI Base class for Command Line Interface app. metacpan
MOP4Import::Base::Configure OO Base class (based on MOP4Import) metacpan
MOP4Import::Declare map import args to C<< $meta->declare_...() >> pragma methods. 0.001_002 metacpan
MOP4Import::FieldSpec metacpan
MOP4Import::Opts metacpan
MOP4Import::PSGIEnv define Env class for PSGI, with extensions. metacpan
MOP4Import::Types create multiple inner-classes at once. metacpan
MOP4Import::Util metacpan
MOP4Import::Util::FindMethods metacpan

Other Files

Build.PL metacpan
Changes metacpan
MANIFEST metacpan
META.json metacpan
META.yml metacpan
README.md metacpan
cpanfile metacpan