[wp-meta] [Making WordPress.org] #2900: incorrect parsing of markdown in @param blocks
Making WordPress.org
noreply at wordpress.org
Tue Jun 27 01:43:59 UTC 2017
#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):
We already partially
[https://meta.trac.wordpress.org/browser/sites/trunk/wordpress.org/public_html
/wp-content/themes/pub/wporg-developer/inc/template-tags.php#L619 handle
for this case] in the `\DevHub\get_params()` function in the wporg-
developer theme.
Doesn't make it any less of a problem, but we have already attempted to
address this on DevHub. Though I notice that we're doing a `str_replace()`
against `$tag` which is an array – should be `$tag['content']`.
Anyway, the problem in this particular case isn't actually bolding, it
looks like the closing `</code>` tag isn't getting parsed properly from
the closing backtick in the description for `$name__like` , which actually
causes everything below it to be `<code>` formatted.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2900#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list