[wp-meta] [Making WordPress.org] #6358: Readme Parsing gets tripped up by new lines in the headers

Making WordPress.org noreply at wordpress.org
Thu Jun 9 01:47:41 UTC 2022


#6358: Readme Parsing gets tripped up by new lines in the headers
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  dd32
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:                    |
------------------------------+---------------------
Changes (by dd32):

 * owner:  (none) => dd32
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"11908" 11908]:
 {{{
 #!CommitTicketReference repository="" revision="11908"
 Plugin Directory: Readme Parser: Be more tolerable of blank lines within
 the headers if it's followed by a valid header.

 This allows for these edgecases to be handled:
  - "Tags: a,b,c\n\nStable Tag: 1.2"
  - "Tags: a,b,c\nStrangeHeader: true\nStable Tag: 1.2"
 along with the expected and valid
  - "tags: a,b,c\nStable Tag: 1.2"

 while also not discarding a Short description just because it contained a
 `:`.

 Props Ipstenu for the report.
 Fixes #6358.
 }}}

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6358#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list