PGObject-Util-DBChange 0.01
- Released by
- EINHVERFR
- Version
- Release Date
- 2016-03-13
- Kwalitee
- 140.62
- Core Kwalitee
- 87.5
- LINKS
PGObject-Util-DBChange 0.01 Deleted
Kwalitee Issues
- no_generated_files
-
Remove the offending files/directories!
Error: Makefile, pm_to_blib
- portable_filenames
-
Rename those files with alphanumerical characters, or maybe remove them because in many cases they are automatically generated for local installation.
Error:
- blib/man3/PGObject::Util::DBChange.3pm
- no_mymeta_files
-
Update MANIFEST.SKIP to exclude MYMETA files. If you are lazy, add "#!install_default" in your MANIFEST.SKIP and update your ExtUtils::Manifest if necessary, then some of the most common files will be excluded.
- 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: PGObject::Util::DBChange::History, PGObject::Util::DBChange::History
- 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: blib/lib/PGObject/Util/DBChange.pm, blib/lib/PGObject/Util/DBChange/History.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: PGObject::Util::DBChange::History, PGObject::Util::DBChange::History
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- 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.