Geo-Postcodes 0.32 Latest
Kwalitee Issues
- meta_yml_conforms_to_known_spec
-
Take a look at the META.yml Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.yml accordingly.
Error: Expected a list structure (author) [Validation: 1.2];Missing mandatory field, 'author' (author) [Validation: 1.2]
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Geo-Postcodes-0.32/lib/Geo/Postcodes/Ajax.pod -- Around line 163: Non-ASCII character seen before =encoding in ''æ','. Assuming CP1252 Geo-Postcodes-0.32/lib/Geo/Postcodes/Selection.pod -- Around line 253: Non-ASCII character seen before =encoding in ''Ã','. Assuming CP1252
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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.311,0.32
- 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.