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: Grimlock, Grimlock::Schema, Grimlock::Schema::Candy, Grimlock::Schema::Result, Grimlock::Schema::Result::Entry, Grimlock::Schema::Result::Role, Grimlock::Schema::Result::Session, Grimlock::Schema::Result::User, Grimlock::Schema::Result::UserRole

prereq_matches_use

List all used modules in META.yml requires

Error:

  • Email::Simple
  • Email::Simple::Creator
  • HTML::Scrubber
  • Try::Tiny

main_module_version_matches_dist_version

Make sure that the main module name and version are the same of the distribution.

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.

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: Grimlock, Grimlock::Schema, Grimlock::Schema::Candy, Grimlock::Schema::Result, Grimlock::Schema::Result::Entry, Grimlock::Schema::Result::Role, Grimlock::Schema::Result::Session, Grimlock::Schema::Result::User, Grimlock::Schema::Result::UserRole, Grimlock::Web::Model::Database, Grimlock::Web::View::HTML, Grimlock::Web::View::JSON

test_prereq_matches_use

List all modules used in the test suite in META.yml test_requires

Error:

  • HTTP::Request::Common

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.01,1

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.

Modules

Name Abstract Version View
Grimlock KING OF CMS metacpan
Grimlock::Schema 1 metacpan
Grimlock::Schema::Candy metacpan
Grimlock::Schema::Result metacpan
Grimlock::Schema::Result::Entry metacpan
Grimlock::Schema::Result::Role metacpan
Grimlock::Schema::Result::Session metacpan
Grimlock::Schema::Result::User metacpan
Grimlock::Schema::Result::UserRole metacpan
Grimlock::Schema::ResultSet::Entry metacpan
Grimlock::Schema::ResultSet::User metacpan
Grimlock::Web Catalyst based application 0.01 metacpan
Grimlock::Web::Controller::API metacpan
Grimlock::Web::Controller::Entry Catalyst Controller metacpan
Grimlock::Web::Controller::Root Root Controller for Grimlock::Web metacpan
Grimlock::Web::Controller::User Catalyst Controller metacpan
Grimlock::Web::Model::Database Catalyst DBIC Schema Model metacpan
Grimlock::Web::Model::Email metacpan
Grimlock::Web::View::HTML Catalyst TT::Bootstrap View metacpan
Grimlock::Web::View::JSON Catalyst JSON View metacpan

Other Files

Changes metacpan
MANIFEST metacpan
META.yml metacpan
Makefile.PL metacpan
README metacpan
dist.ini metacpan