mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 17:26:22 +03:00
[GH-ISSUE #223] Additional style check for fenced code block: backticks vs quotes #2038
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#2038
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 @RedX2501 on GitHub (Sep 27, 2019).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/223
Currently rule MD046 only checks for indented vs fenced but it seems that some dialects of markdown allow fencing to use
~~~over```.It would be nice if a new rule was added (or MD046 expanded) where you could define whether fenced code blocks uses tildes, backticks or it should be consistent. Pretty much how lists work.
See https://sourceforge.net/p/tilde/wiki/markdown_syntax/ and https://www.markdownguide.org/extended-syntax/#fenced-code-blocks for two examples where ~ is allowed.
@DavidAnson commented on GitHub (Sep 27, 2019):
Agreed. https://spec.commonmark.org/0.29/#fenced-code-blocks