| Subject: | Support linefeeds in abstract parsing. |
Presently, if there is a \n encountered in the NAME - DESCRIPTION part of a POD document, the description will be terminated at the \n.
https://metacpan.org/source/MSCHWERN/ExtUtils-MakeMaker-6.62/lib/ExtUtils/MM_Unix.pm#L2604
An example of this occurring in the wild is as follows:
https://metacpan.org/source/BOBTFISH/Catalyst-Plugin-Authentication-0.10020/Makefile.PL
And the POD in Question is here:
https://metacpan.org/source/BOBTFISH/Catalyst-Plugin-Authentication-0.10020/lib/Catalyst/Plugin/Authentication.pm#L485
And the resulting YAML:
https://metacpan.org/source/BOBTFISH/Catalyst-Plugin-Authentication-0.10020/META.yml
And API-ified JSON:
http://api.metacpan.org/v0/release/_search?q=name:Catalyst-Plugin-Authentication-0.10020&fields=abstract,license
Obviously this isn't quite what the author intended the abstract to be, and I have resulting opened https://rt.cpan.org/Ticket/Display.html?id=77028
But it makes some degree of sense to me that abstract parsing should probably try to ignore line breaks in the description.