section starts need double newline
See original GitHub issueUsing 6.11.4, the following input is not handled as well as with other tools.
### S1
C1
### S2
C2
Actual
The second triple-hash is not treated as a new section.

Expected
Two sections (github’s own preview seems to handle this fine, as does vscode’s, as does https://dillinger.io/, etc.). E.g. when i place a newline before the second section:
### S1
C1
### S2
C2
then markdown-to-jsx parses it as do the other tools (without the extra newline):

Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7
Top Results From Across the Web
Line break in section name
I have tried double-\ but it breaks the line in the ToC as well. And it does break the line, but the new...
Read more >Java add new line after a sentence ( why double ...
A \n newline character starts a new line immediately under the previous line with no gap. If you want a blank line between...
Read more >The Dos and Don'ts of Adding an HTML Line Break
Learn what a line break is, how to add one in HTML, and why a line break might not be working in your...
Read more >Handle line breaks (newlines) in Python - nkmk note
This article describes how to handle strings including line breaks (line feeds, new lines) in Python. Create a string containing line breaks.
Read more >Line breaks and blank spaces
However, leaving an empty line starts a new paragraph. ... is not the only command to insert line breaks, in the next section...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
fwiw, we have switched to react-markdown which, under the covers, uses remark-parse for parsing. With react-markdown v5 (which uses remark-parse v9), we have found the parsing to be pretty robust (v4/v8 had several parser bugs that impacted us, but v5/v9 seems pretty good)
Using 7.1.3 still not changed,maybe author already forget this,let me mention @probablyup