prereqs => CPAN::Meta->load_file('Dist-Foo-0.001/META.json')->effective_prereqs,
new_prereqs => CPAN::Meta->load_file('Dist-Foo-0.002/META.json')->effective_prereqs,
});
print $changes->seria
> [@ignore_files],
},
);
$self->add_plugin( 'License' => {} );
$self->add_plugin( 'MetaJSON' => {} );
$self->add_plugin( 'MetaYAML::Minimal' => {} );
$self->add_p
JSON v1.1.0
{
"namespace":"Dist::Zilla::PluginBundle::Author::KENTNL",
"interface":"class",
"inherits":"Moose::Object",
"does":"Dist::Zilla::Role::PluginBundle"
}
=end MetaPOD::JSON
rsion 2.025021
=head1 SYNOPSIS
dzil new -P Author::KENTNL Some::Dist::Name
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Dist::Zilla::MintingProfile::Author::KENTNL",
"inherits":"Moose::O
"does":"Dist::Zilla::Role::MintingProfile::ShareDir",
"interface":"class"
}
=end MetaPOD::JSON
=head1 AUTHOR
Kent Fredric <kentnl@cpan.org>
=head1 COPYRIGHT AND LICENSE
This software is co
prereqs => CPAN::Meta->load_file('Dist-Foo-1.01/META.json')->effective_prereqs,
my $new_prereqs => CPAN::Meta->load_file('Dist-Foo-1.01/META.json')->effective_prereqs,
my $group = CPAN::Changes:
_prereqs => CPAN::Meta->load_file('Dist-Foo-1.01/META.json')->effective_prereqs,
old_prereqs => CPAN::Meta->load_file('Dist-Foo-1.00/META.json')->effective_prereqs,
);
# Currently slightly co
ance, this L<diff|https://metacpan.org/diff/file?target=ETHER/Moose-2.1210/META.json&source=ETHER/Moose-2.1005/META.json> would display as:
[ Dependencies::Stats ]
- configure: +2
- develop
D::JSON v1.1.0
{
"namespace":"CPAN::Changes::Markdown::Filter",
"interface":"class",
"inherits":"Moo::Object",
"does":"CPAN::Changes::Markdown::Role::Filter"
}
=end MetaPOD::JSON
=
process a line.
=begin MetaPOD::JSON v1.1.0
{
"namespace":"CPAN::Changes::Markdown",
"interface":"class",
"inherits":"Moo::Object"
}
=end MetaPOD::JSON
=head1 AUTHOR
Kent Fredric <ke
vice::SQLFormat;
$WebService::SQLFormat::VERSION = '0.000007';
use Moo 2.002004;
use JSON::MaybeXS qw( decode_json );
use LWP::UserAgent ();
use Module::Runtime qw( use_module );
use Types::Standard
=> $sql,
strip_comments => $self->strip_comments,
}
);
return decode_json( $res->decoded_content )->{result};
}
1;
=pod
=encoding UTF-8
=head1 NAME
WebService::SQLFor
e is logic that
would be the same if the resource generated by the view was a different type (say
JSON or XML) then its likely that logic belongs in the controller. However I
encourage you to choose
not specified.
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Git::Wrapper::Plus::Tags",
"interface":"class",
"inherits":"Moo::Object"
}
=end MetaPOD::JSON
=head1 AUTHOR
Kent Fredric <k
s is a L<< C<Dist::Zilla>|Dist::Zilla >> Plugin that populates the C<provides>
property of C<META.json> and C<META.yml> by absorbing it from your shipped modules,
in a manner similar to how C<PAUSE> i
k
This parameter may be specified multiple times to aggregate a list of finders
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Dist::Zilla::Plugin::MetaProvides::Package",
"interface":"class",
herits":"Moose::Object",
"does":"Dist::Zilla::Role::MetaProvider::Provider"
}
=end MetaPOD::JSON
=head1 OPTIONS INHERITED FROM L<Dist::Zilla::Role::MetaProvider::Provider>
=head2 L<< C<inherit
ns a match if any child of C<path> exists matching the regexp C<basename_regexp>
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Path::IsDev::Heuristic::Changelog",
"interface":"single_class",
:Heuristic", "Path::IsDev::Role::Matcher::Child::BaseName::MatchRegexp::File" ]
}
=end MetaPOD::JSON
=head1 AUTHOR
Kent Fredric <kentnl@cpan.org>
=head1 COPYRIGHT AND LICENSE
This software is co
lt
version = 1.4 ; default
=head1 DESCRIPTION
Generally, if you're creating both C<META.json> and C<META.yml>, then you're doing so purely for compatibility reasons.
In such circumstances,
on is for such circumstances.
However, if you are I<only> shipping C<META.yml> and B<NOT> C<META.json>, then using this extension
would be harmful and cause loss of information.
Presently, this exte
:META;
our $VERSION = '1.001003';
# ABSTRACT: Determine if a path contains META.(json|yml)
our $AUTHORITY = 'cpan:KENTNL'; # AUTHORITY
use Role::Tiny::With qw( with );
with 'Path::I
, 'Path::IsDev::Role::Matcher::Child::Exists::Any::File';
sub files {
return qw( META.json META.yml );
}
sub matches {
my ( $self, $result_object ) = @_;
if ( $self->child_exist
- Determine if a path contains META.(json|yml)
=head1 VERSION
version 1.001003
=head1 METHODS
=head2 C<files>
files relevant to this heuristic:
META.json
META.yml
=head2 C<matches>
Mat
role.
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Dist::Zilla::MetaProvides::Types",
"interface":"exporter",
"inherits":"MooseX::Types::Base"
}
=end MetaPOD::JSON
=head1 SEE ALSO
=ove
tches>
Matches if any of the files in C<files> exist as children of the C<path>
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Path::IsDev::Heuristic::Makefile",
"interface":"single_class",
euristic",
"Path::IsDev::Role::Matcher::Child::Exists::Any::File"
]
}
=end MetaPOD::JSON
=head1 AUTHOR
Kent Fredric <kentnl@cpan.org>
=head1 COPYRIGHT AND LICENSE
This software is co
:Heuristic::MYMETA;
our $VERSION = '1.001003';
# ABSTRACT: Determine if a path contains MYMETA.(json|yml)
our $AUTHORITY = 'cpan:KENTNL'; # AUTHORITY
use Role::Tiny::With qw( with )
'Path::IsDev::Role::Matcher::Child::Exists::Any::File';
sub files {
return qw( MYMETA.json MYMETA.yml );
}
sub matches {
my ( $self, $result_object ) = @_;
if ( $self->child_exi
ncoding UTF-8
=head1 NAME
Path::IsDev::Heuristic::MYMETA - Determine if a path contains MYMETA.(json|yml)
=head1 VERSION
version 1.001003
=head1 DESCRIPTION
This heuristic is intended as a guara
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Dist::Zilla::Role::MetaProvider::Provider",
"interface":"role",
"does":"Dist::Zilla::Role::MetaProvider"
}
=end MetaPOD::JSON
=head1 SEE ALS
vider>
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Dist::Zilla::MetaProvides::ProvideRecord",
"interface":"class",
"inherits":"Moose::Object"
}
=end MetaPOD::JSON
=head1 AUTHOR
Kent F
type
positive heuristic
=begin MetaPOD::JSON v1.1.0
{
"namespace":"Path::IsDev::Role::Heuristic",
"interface":"role"
}
=end MetaPOD::JSON
=head1 AUTHOR
Kent Fredric <kentnl@cpan.org