DBIx-Recordset 0.23
Kwalitee Issues
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- has_human_readable_license
-
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
- has_license_in_source_file
-
Add =head1 LICENSE and the text of the license to the main module in your code.
- 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: DBIx::Compat
- prereq_matches_use
-
List all used modules in META.yml requires
Error:
- DBI
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: DBIx-Recordset-0.23/Compat.pm -- Around line 514: '=item' outside of any '=over' Around line 536: You forgot a '=back' before '=head1' DBIx-Recordset-0.23/Recordset/DBSeq.pm -- Around line 161: '=item' outside of any '=over' =over without closing =back DBIx-Recordset-0.23/Recordset/FileSeq.pm -- Around line 194: '=item' outside of any '=over' =over without closing =back DBIx-Recordset-0.23/Recordset.pm -- Around line 3889: '=item' outside of any '=over' Around line 4239: You forgot a '=back' before '=head2' Around line 4241: '=item' outside of any '=over' Around line 4322: You forgot a '=back' before '=head2' Around line 4326: '=item' outside of any '=over' Around line 4420: You forgot a '=back' before '=head2' Around line 4422: '=item' outside of any '=over' Around line 4488: You forgot a '=back' before '=head2' Around line 4492: '=item' outside of any '=over' Around line 4513: You forgot a '=back' before '=head1' Around line 5341: '=item' outside of any '=over' Around line 5345: You forgot a '=back' before '=head1' Around line 5474: '=item' outside of any '=over' Around line 5506: You forgot a '=back' before '=head1' Around line 5790: '=item' outside of any '=over' =over without closing =back
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- has_tests_in_t_dir
-
Add tests or move tests.pl to the t/ directory!
- no_stdin_for_prompting
-
Use the prompt() method from ExtUtils::MakeMaker/Module::Build.
- 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: Compat.pm, Database.pm, Recordset.pm, Recordset/DBSeq.pm, Recordset/FileSeq.pm
- meta_yml_has_license
-
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
- has_known_license_in_source_file
-
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
- 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: DBIx::Compat, DBIx::Database, DBIx::Recordset, DBIx::Recordset::DBSeq, DBIx::Recordset::FileSeq
- 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 |
---|---|---|---|
DBIx::Compat | Perl extension for Compatibility Infos about DBD Drivers | metacpan | |
DBIx::Database | metacpan | ||
DBIx::Recordset | Perl extension for DBI recordsets | 0.23 | metacpan |
DBIx::Recordset::DBSeq | Sequence generator in DBI database | metacpan | |
DBIx::Recordset::FileSeq | Sequence generator in Filesystem | metacpan |