Search results for "module:Perl::Critic::Policy::Documentation::RequirePackageMatchesPodName"

Perl::Critic::Policy::Documentation::RequirePackageMatchesPodName - The =head1 NAME section should match the package. River stage three • 131 direct dependents • 386 total dependents

PETDANCE/Perl-Critic-1.144 - 06 Dec 2022 04:59:59 UTC

Perl::Critic::Policy::Documentation::ProhibitLinkToSelf - don't Lltgt link to own POD River stage two • 5 direct dependents • 18 total dependents

This policy is part of the "Perl::Critic::Pulp" add-on. It asks you not to use "L<>" markup to refer to a POD document itself. =head1 NAME My::Package - something =head1 DESCRIPTION L<My::Package> does blah blah ... # bad =head1 SEE ALSO L<My::Packag...

KRYDE/Perl-Critic-Pulp-99 - 28 Feb 2021 08:34:14 UTC

Perl::Critic::Policy::Documentation::ProhibitBadAproposMarkup - don't use Cltgt markup in a NAME section River stage two • 5 direct dependents • 18 total dependents

This policy is part of the "Perl::Critic::Pulp" add-on. It asks you not to write C<> markup in the NAME section of the POD because it comes out badly in the man-db "apropos" database. For example, =head1 NAME foo - like the C<bar> program # bad "pod2...

KRYDE/Perl-Critic-Pulp-99 - 28 Feb 2021 08:34:14 UTC
3 results (0.066 seconds)