mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 01:36:03 +03:00
[GH-ISSUE #427] MD037 false positives with * in a <code> #356
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#356
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @regseb on GitHub (Sep 12, 2021).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/427
The no-space-in-emphasis rule (MD037) displays false positives with
*in a<code>tag. There is no problem with`. Maybe the text in<code>isn't interpreted as inCode.@DavidAnson commented on GitHub (Sep 12, 2021):
MD037 only recognizes Markdown code sections using backtick or indent. HTML tags are discouraged (MD033) and ignored by this rule.
@regseb commented on GitHub (Sep 12, 2021):
I have a big table in my README. I use the
<table>tag to format the code (with line breaks for example). But markdown isn't interpreted in the<table>tag, so I use HTML tags (<code>,<a>...).@DavidAnson commented on GitHub (Sep 12, 2021):
I understand what you are doing here, but I am reluctant to add support for HTML tags to the various Markdown rules that have corresponding HTML syntax. By rough approximation it looks like maybe half of the current rules could be applied to HTML as well. It's challenging enough to implement flexible Markdown parsing; doing the same for HTML may be too much. (It's true that I made an exception for MD041, but that was for a very common scenario that's well constrained.)