mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 17:56:02 +03:00
[GH-ISSUE #670] Add rule to whitelist allowed languages in code fences #498
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#498
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 @Lunkentuss on GitHub (Dec 7, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/670
I often find that languages in code fences contains typos or various alternative spellings, such as "yml" and "yaml" across the repository. This can have critical consequences when tools will only enable syntax highlighting for certain spellings. Therefor it would be nice to have a rule, which is disabled by default to allow backwards compatability, to only allow certain languages.
With the overridden rule, using a fence block such as
will fail. I don't know if it makes sense to incorporate this with rule MD040 or not.
@Lunkentuss commented on GitHub (Dec 7, 2022):
I'm closing this since I realized a similar issue already exists: https://github.com/DavidAnson/markdownlint/issues/608