MacDownApp / MacDownApp/macdown
new line shouldn't be required before fenced codeblock
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 9.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
It seems that a new line is required before a fenced code block, it shouldn't be.
``````
text
```
fenced code block
```
``````
http://johnmacfarlane.net/babelmark2/?text=no+need+for+new+line%0A%60%60%60%0Abefore+fenced+code+block%0A%60%60%60
Presumably this is an issue upstream?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the reported input with the linked Babelmark result and confirm whether the behavior is specific to MacDown or an upstream Markdown parser. No file or test is named in the issue, so identify the parser entry point before determining how the missing newline is handled; done means fenced code blocks render correctly without a preceding blank line or the issue is confirmed upstream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100