erwise, Kwalify is unhappy with
# data elements set to false.
local $YAML::XS::Boolean = 'JSON::PP';
# Load the metadata and check it against the schema. YAML::XS for some
# reason p
he \z }xms,
qr{ \A Build \z }xms,
qr{ \A MANIFEST[.]bak \z }xms,
qr{ \A MYMETA [.] (?:json (?:[.]lock)? | yml) \z }xms,
qr{ \A _build \z }xms,
qr{ \A blib \z }xms,
qr{ \A confi
##########
1;
__END__
=for stopwords
Allbery DocKnot MERCHANTABILITY NONINFRINGEMENT sublicense JSON CPAN ARGS
distdir Automake xz gpg Kwalify IO-Compress-Lzma
=head1 NAME
App::DocKnot::Dist - Pre
rnings;
use Carp qw(croak);
use JSON::MaybeXS qw(JSON);
use Kwalify qw(validate);
use Path::Iterator::Rule;
use Path::Tiny qw(path);
use YAML::XS ();
# The older JSON metadata format stored text sni
ey contains a slash, like
# foo/bar, it will be stored as a nested hash, as $data{foo}{bar}.
our @JSON_METADATA_FILES = qw(
bootstrap
build/middle
build/suffix
debian/summary
packa
test/suffix
);
##############################################################################
# JSON helper methods
##############################################################################
#
######
1;
__END__
=for stopwords
Allbery DocKnot MERCHANTABILITY NONINFRINGEMENT XDG sublicense JSON CPAN
ARGS Kwalify
=head1 NAME
App::DocKnot::Generate - Generate documentation from package meta
enerating consistent
human-readable software package documentation from metadata files, primarily
JSON and files containing documentation snippets. It takes as input a
directory of metadata and a set
f IO-Compress-Lzma), IO::Uncompress::Gunzip (part of
IO-Compress), IPC::Run, IPC::System::Simple, JSON::MaybeXS, Kwalify,
List::SomeUtils, Path::Iterator::Rule, Path::Tiny, Perl6::Slurp, Template
(par