[GH-ISSUE #1455] Accept Micromark config in `lint` options #686

New issue

Closed

opened 2026-03-03 01:29:05 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:29:05 +03:00

Owner

Originally created by @farnabaz on GitHub (Dec 20, 2024).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1455

Currently, we can extend MarkdownIt using options.markdownItPlugins, but it is not possible to pass extensions to micromark.

It would be great to provide an option to pass Micromark extensions and configs to extend it

Originally created by @farnabaz on GitHub (Dec 20, 2024). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1455 Currently, we can extend MarkdownIt using `options.markdownItPlugins`, but it is not possible to pass extensions to micromark. It would be great to provide an option to pass Micromark extensions and configs to extend it

kerem

2026-03-03 01:29:05 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:29:06 +03:00

Author

Owner

@DavidAnson commented on GitHub (Dec 21, 2024):

I was wondering when this might come up. :)

I’d prefer not to support custom micromark plugins if I don’t have to because that adds complexity and maintenance overhead and is tied to a specific parser. I don’t see significant use of markdownItPlugins across all of GitHub (see query below), and have been taking the approach of incorporating common micromark extensions by default.

What is your scenario? What micromark extension are you looking to add?

Here’s a quick GitHub query I did to filters out clones and forks of my code:

https://github.com/search?q=markdownlint+AND+markdownItPlugins+NOT+path%3A.md+NOT+path%3A.d.ts+NOT+path%3A.d.mts+NOT+path%3A.html+NOT+path%3Atest+NOT+path%3Amarkdownlint-browser+NOT+path%3Aconfig-schema+NOT+path%3Amarkdownlint.js+NOT+path%3Amarkdownlint.mjs+NOT+path%3Amarkdownlint-cli2.js+NOT+path%3Amarkdownit.cjs+NOT+path%3Atype-check.ts+NOT+path%3Aextension.js+NOT+markdownlint-rule-sample&type=code&p=1

As far as I can tell, there’s just one repo that MIGHT be using this feature (and I don’t see evidence it actually is):

https://github.com/diplodoc-platform/transform/blob/5bf44fd28a48f00f4cdcfa9fc75d3180bf11d157/src/transform/yfmlint/index.ts

@DavidAnson commented on GitHub (Dec 21, 2024): I was wondering when this might come up. :) I’d prefer not to support custom `micromark` plugins if I don’t have to because that adds complexity and maintenance overhead and is tied to a specific parser. I don’t see significant use of `markdownItPlugins` across all of GitHub (see query below), and have been taking the approach of incorporating common `micromark` extensions by default. What is your scenario? What `micromark` extension are you looking to add? -- Here’s a quick GitHub query I did to filters out clones and forks of my code: <https://github.com/search?q=markdownlint+AND+markdownItPlugins+NOT+path%3A.md+NOT+path%3A.d.ts+NOT+path%3A.d.mts+NOT+path%3A.html+NOT+path%3Atest+NOT+path%3Amarkdownlint-browser+NOT+path%3Aconfig-schema+NOT+path%3Amarkdownlint.js+NOT+path%3Amarkdownlint.mjs+NOT+path%3Amarkdownlint-cli2.js+NOT+path%3Amarkdownit.cjs+NOT+path%3Atype-check.ts+NOT+path%3Aextension.js+NOT+markdownlint-rule-sample&type=code&p=1> As far as I can tell, there’s just one repo that MIGHT be using this feature (and I don’t see evidence it actually is): <https://github.com/diplodoc-platform/transform/blob/5bf44fd28a48f00f4cdcfa9fc75d3180bf11d157/src/transform/yfmlint/index.ts>

kerem referenced this issue

2026-03-07 20:07:01 +03:00

[GH-ISSUE #686] MD052: "Error: Property 'range' of onError parameter is incorrect." #2358

kerem referenced this issue

2026-03-07 20:07:08 +03:00

[GH-ISSUE #733] MD052 and brackets #2373