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.

Add an option allowed_languages to the fenced-code-language

See original GitHub issue

Add an option allowed_languages to the fenced-code-language rule to define the allowed languages. With this option, markdownlint will be able to check:

name consistency (javascript / js);
case (html / HTML);
typos (markdown / markdonw)
unsupported languages (json / jfather).

Issue Analytics

State:
Created a year ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

regsebcommented, Nov 4, 2022

I didn’t see that there was already the #608 issue. 😞

I looked at the commit, the languages are case insensitive. You could add ignoreCase option to check case (html / HTML).

0reactions

nschonnicommented, Nov 5, 2022

I think skipping the ignoreCase might be an easy sell, if the casing would be fixable based on the allowed values. That would probably add a bunch of complication though

Top Results From Across the Web

DavidAnson Markdownlint Issues - IssueHint

Add rule to whitelist allowed languages in code fences ... Add an option allowed_languages to the fenced-code-language, open, 8, 2022-11-04, 2022-12-03.