The parser does not look far enough ahead. It sees the text of the heading that follows it, and thinks that text is a part of the list (list items with blank lines in are a valid syntax for lists with multi-paragraph contents). It does not spot the "----------" that follows the heading text which turns it into an actual heading. The alternate heading syntax (##) allows the list parsing to spot that though, as it does not need to look any further than the heading line. I've submitted a PR for this.
-- Jason On Friday, 13 January 2017 10:46:29 UTC, David Négrier wrote: > > ... > > Regarding your last issue: > > > There's a formatting issue in the metadoc, 9.3, contributors: Taylor > > Otwell is separated from the rest of the group for some reason. I'm > > sure there's nothing to be read into that. :-) > > Poor Taylor! :) I've looked at the markdown file and can't find anything > weird there. Unless someone can point me to a mistake I did not see, I > believe the error spurs from Github markdown parser that is adding an > additional <p> in the <li> of Taylor for no reason. This does not seems to > happen with other markdown parsers... anyone would have a workaround for > this? > > ++ > David. > > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/abb9de0a-0e29-43e4-b0d0-3ecd5a99b12b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
