Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Markdown header issue.
See original GitHub issueHey,
I think I found a “bug” in markdown.
When I type the following, only the ===== gets classes for being a header, and the text Header does not. I think either both should get this class or none of the two, or maybe the ====== could get an additionally class, if neither of the above work. Otherwise it makes it hard to style correctly. Thanks.
Header
======
Issue Analytics
- State:
- Created 10 years ago
- Reactions:2
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Basic Syntax - Markdown Guide
Headings. To create a heading, add number signs ( # ) in front of a word or phrase. ... This can result in...
Read more >Markdown headers not rendering properly - GitLab.org
Summary Rendering headers in a simple README.md produces inconsistent results. ... Use tasks to break down this issue into smaller parts.
Read more >Header anchors [needs discussion] · Issue #28 - GitHub
It's very popular request to add header ancors. Prior to do it, we need to discuss possible security problems and solutions. Read first....
Read more >Markdown Syntax Documentation - Daring Fireball
Thus, Markdown's formatting syntax only addresses issues that can be ... or <del> — can be used anywhere in a Markdown paragraph, list...
Read more >How to link to part of the same document in Markdown?
If your header contains multiple words, "Like this one", replace spaces with hyphens in the anchor [just](#like-this-one) . – Mogsdad. Feb 4, 2016...
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
Made a quick naive fix in this branch over here. It’s still not 100% CM-compliant, but it fixes styling for the line immediately before the
------setext line.Also not sure if it doesn’t have some major performance implications. Do we have some perf benchmarks we could run on this?
Any possibility of this issue getting reopened as a feature request? It would be very nice if the workaround posted by brondsem wasn’t necessary.