RPC-Lite 0.20 Latest
Kwalitee Issues
- 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: RPC::Lite::Threading, RPC::Lite::Transport
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: RPC-Lite-0.20/lib/RPC/Lite/Client.pm -- Around line 43: You can't have =items (as at line 60) unless the first thing after the =over is an =item =over without closing =back RPC-Lite-0.20/lib/RPC/Lite/Request.pm -- Around line 18: You can't have =items (as at line 24) unless the first thing after the =over is an =item RPC-Lite-0.20/lib/RPC/Lite/Response.pm -- Around line 18: You can't have =items (as at line 24) unless the first thing after the =over is an =item RPC-Lite-0.20/lib/RPC/Lite/Serializer.pm -- Around line 23: You can't have =items (as at line 29) unless the first thing after the =over is an =item RPC-Lite-0.20/lib/RPC/Lite/Session.pm -- Around line 29: You can't have =items (as at line 97) unless the first thing after the =over is an =item =over without closing =back RPC-Lite-0.20/lib/RPC/Lite/SessionManager.pm -- Around line 31: You can't have =items (as at line 129) unless the first thing after the =over is an =item =over without closing =back RPC-Lite-0.20/lib/RPC/Lite/Signature.pm -- Around line 32: You can't have =items (as at line 50) unless the first thing after the =over is an =item =over without closing =back RPC-Lite-0.20/lib/RPC/Lite/Transport.pm -- Around line 95: =back without =over
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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: RPC::Lite, RPC::Lite::Client, RPC::Lite::Error, RPC::Lite::MessageQuantizer, RPC::Lite::Notification, RPC::Lite::Request, RPC::Lite::Response, RPC::Lite::Serializer, RPC::Lite::Serializer::JSON, RPC::Lite::Serializer::Null, RPC::Lite::Serializer::XML, RPC::Lite::Server, RPC::Lite::Session, RPC::Lite::SessionManager, RPC::Lite::Signature, RPC::Lite::Threading, RPC::Lite::Transport, RPC::Lite::Transport::TCP
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.1,0.20
- 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.