[wp-meta] [Making WordPress.org] #197: Parser doesn't recognize line breaks and/or lists

[Making WordPress.org]

#197: Parser doesn't recognize line breaks and/or lists
---------------------------+-------------------------------------
  Reporter:  samuelsidler  |      Owner:
      Type:  defect        |     Status:  closed
  Priority:  high          |  Component:  developer.wordpress.org
Resolution:  fixed         |   Keywords:
---------------------------+-------------------------------------
Changes (by coffee2code):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Formatting of parsed content in general should be much improved now.

 Previously linebreaks in parsed docs would be translated to `<br>`,
 causing the text to be unnecessarily narrow in the Code Ref. This was
 fixed on the parser side of things (see [https://github.com/rmccue/WP-
 Parser/commit/9e18724e6eb413f4f163f8b2660a30afeaf40719 1],
 [https://github.com/rmccue/WP-
 Parser/commit/d5805847867fc929296e3b17df24212af2b9798f 2]).

 The specifically referenced issue in the ticket has been indirectly
 addressed globally. The WP 4.0 release included a docs initiative to
 document params that accept a keyed array argument(s) (e.g. the $postarr
 from the ticket-referenced function). Part of that effort was to move such
 existing argument documentation into the more appropriate Parameters
 section and document it according to a more rigorous guideline.

 Granted, in so doing, the introduction of the new parameter notation means
 the parser doesn't parse the hash for its requisite parts (it's just a
 run-on string for now) which meant its unaffected display was also be a
 run-on block of text. A [https://meta.trac.wordpress.org/changeset/836
 temporary solution] has been implemented (which can do with some
 iteration), but we'll have to address this in both the parser and theme
 before long.

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