[wp-meta] [Making WordPress.org] #1216: Parsing readme files fails on code blocks starting with `#

[Making WordPress.org]

#1216: Parsing readme files fails on code blocks starting with `#
-------------------------+------------------------------
  Reporter:  DvanKooten  |      Owner:
      Type:  defect      |     Status:  closed
  Priority:  normal      |  Component:  Plugin Directory
Resolution:  wontfix     |   Keywords:
-------------------------+------------------------------

Comment (by barrykooij):

 Replying to [comment:3 DvanKooten]:
 > @Otto42 Not even inside code blocks? I mean, it's pretty common to have
 CSS examples (using ID's) in your plugin FAQ...

 And one could even comment in PHP with #. Not every hashtag means someone
 is trying to type Markdown.

 @Otto42
 What is the reason this is instantly closed instead of asking what the
 intention of the hashtag was?

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