We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Used via Dist::Milla it creates an empty README.md, if the pod is placed in an package after
package Foo; # some code __DATA__ @@ something here __END__ =pod here
Had to move the pod before DATA
See https://github.com/wollmers/Mojolicious-Plugin-ServerInfo/commits/master/README.md
Other readers like perldoc have no problems extracting the pod.
The text was updated successfully, but these errors were encountered:
ReadmeAnyFromPod uses PPI to extract the POD, so I guess this is a bug in PPI?
https://github.com/DarwinAwardWinner/Dist-Zilla-Plugin-ReadmeAnyFromPod/blob/master/lib/Dist/Zilla/Plugin/ReadmeAnyFromPod.pm#L373-376]
Sorry, something went wrong.
Sure enough, it is a PPI Issue: Perl-Critic/PPI#15 Perl-Critic/PPI#16
I'm going to close this since there's nothing I can do about it in this module.
No branches or pull requests
Used via Dist::Milla it creates an empty README.md, if the pod is placed in an package after
Had to move the pod before DATA
See https://github.com/wollmers/Mojolicious-Plugin-ServerInfo/commits/master/README.md
Other readers like perldoc have no problems extracting the pod.
The text was updated successfully, but these errors were encountered: