New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix POD errors #10

Merged
merged 2 commits into from Nov 1, 2015

Conversation

Projects
None yet
2 participants
@paultcochrane
Contributor

paultcochrane commented Nov 1, 2015

podchecker found some errors in the modules POD. These changes correct the errors.

paultcochrane added some commits Nov 1, 2015

Move text into POD block
The text here shouldn't be an argument to the `=pod` directive (which
doesn't take arguments), it should be moved to the next line.

This fixes the pod error:

    *** ERROR: Spurious text after =pod at line 12 in file ./lib/Plack/App/FakeModPerl1.pm
Add newline after =cut directives
POD requires that a empty line appears after a `=cut` directive.  This
change fixes the POD errors:

    *** ERROR: Spurious text after =cut at line 69 in file ./lib/Plack/App/FakeModPerl1/Dispatcher.pm
    *** ERROR: Spurious text after =cut at line 16 in file ./lib/Plack/App/FakeModPerl1.pm

chiselwright added a commit that referenced this pull request Nov 1, 2015

@chiselwright chiselwright merged commit 8d698ce into chiselwright:master Nov 1, 2015

chiselwright added a commit that referenced this pull request Nov 15, 2015

v0.0.5
 - Merged pull-requests from Paul Cochrane:
   - #6 replace NoTabsTests
   - #7 add missing abstracts (for dzil)
   - #8 add Travis config
   - #9 purge trailing whitespace
   - #10 fix POD errors
   - #11 update dist.ini
   - #12 add missing strictures
   - #13 remove shebang in tests
   - #14 fix typos in POD
   - #15 fix tests on non-English locales
   - #16 increase error severity in call handler
 - Resolve "[PkgVersion] no blank line for $VERSION after package" with dzil prep
 - add skeleton POD for methods
   unhelpfully empty but keeps pod-coverage tests happy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment