[wp-meta] [Making WordPress.org] #2900: incorrect parsing of markdown in @param blocks

[Making WordPress.org]

#2900: incorrect parsing of markdown in @param blocks
-----------------------------+------------------
 Reporter:  pbiron           |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Developer Hub    |  Resolution:
 Keywords:  has-screenshots  |
-----------------------------+------------------

Comment (by DrewAPicture):

 Assuming we fix the `$tag` vs `$tag['content']` thing, there's a still a
 problem with an opening `<code>` tag where it should be a closing
 `</code>` tag.

 Here's what the raw section description looks like coming from parsedown
 before wporg-developer manipulates it for display:


 {{{
 Retrieve terms with criteria by which a term is LIKE
 `$name__like<code>. Default empty.     @type string
 $description__like
 }}}

 Following the fixed `str_replace()`, this is what we get:
 {{{
 Retrieve terms with criteria by which a term is LIKE
 `$name</strong>like<code>. Default empty.     @type string
 $description__like
 }}}

 Note the presence of the backtick before `$name` and `<code>` after
 `like_`

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