MacDownApp / MacDownApp/macdown
Update header parser for apparent changes to GitHub
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
Headers in Markdown are specified like this:
##This is an H2
This should render like so in GitHub:
This in an H2
However, I've recently noticed that headers specified without a space between the # and the first character are rendering as ##This is an H2 on GitHub pages. I'm not sure if this is intentional, but MacDown should match GitHub's behavior.
Here's a test H2 without the space, so we can see if GitHub has changed their behavior:
##This is an H2 without a space
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 reproducing the Markdown example in MacDown and compare its rendering with the GitHub behavior described in the issue. Trace the Markdown parsing or rendering entry point used for headers without a space after the hash marks. Done means MacDown matches GitHub's current output for that example, with a regression check for the no-space H2 case.
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