mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 01:05:55 +03:00
[GH-ISSUE #412] markdown-disable-next-line works on same line, not next line #344
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#344
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 @mpoundstone on GitHub (Jul 28, 2021).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/412
I'm still getting problems returned from markdownlint for lines even when I add the
<!-- markdownlint-disable-next-line -->function above a line.For example:
I want to disable markdownlint for
* Test list item with asteriskonly but it's still returning a problem:MD004/ul-style: Unordered list style [Expected: dash; Actual: asterisk]. Even when I specify:or
It still returns the MD004: ul-style problem. But it stops returning all problems when I put the disable function in the same line.
And if I try to do the following,
I'm returned with the following problem:
MD032/blanks-around-lists: Lists should be surrounded by blank lines.Is this a bug? Or have I made a mistake with my syntax somewhere?
@DavidAnson commented on GitHub (Jul 28, 2021):
Your first example seems to work perfectly as-is: https://dlaa.me/markdownlint/#%25m%23%20Issue%20412%0A%0A-%20Test%20list%20item%0A%20%20%0A%3C!--%20markdownlint-disable-next-line%20--%3E%0A*%20Test%20list%20item%20with%20asterisk%0A%20%20%0A-%20Test%20list%20item%0A
Where are you seeing a problem?
@mpoundstone commented on GitHub (Jul 29, 2021):
Ah, looks like I can no longer recreate the issue in my VSCode environment. Possible conflict with another extension.
Apologies for the bother and thank you for responding so quickly!