David Anson

The existing issues you've linked to seem to cover most of what you describe here. What is new or unique for this issue?

Right, the VS Code markdownlint extension uses the Node implementation of markdownlint, not this one.

Thinking about this very briefly, I feel like this rule should peek at any customizations applied to other built-in rules and respect them. (Although right now it does not have...

Rules are meant to be independent, and what I propose here would obviously not coordinate with any custom rules. There is no precedent for this, but it's the option I...

Thanks for bringing this to my attention! As you probably know, CodeQL raises issues for this problem, and I spent time one or two releases ago addressing all of the...

```diff diff --git a/.eslintrc.json b/.eslintrc.json index 46e07bb..8627726 100644 --- a/.eslintrc.json +++ b/.eslintrc.json @@ -7,6 +7,7 @@ "eslint:all", "plugin:jsdoc/recommended", "plugin:n/recommended", + "plugin:regexp/recommended", "plugin:unicorn/all" ], "ignorePatterns": [ diff --git a/package.json b/package.json index...

FYI, the property called "docs" in this PR is called "information" in the Node.js implementation of markdownlint. Maybe it is interesting to match that.

Yeah, sorry I didn't notice the inconsistency when this change was in PR.

@jaymzh You should probably remove my name from the maintainers list at some point. I am subscribed to this repo and pay attention to what's going on, but I am...

This looks like an oversight. I'll implement this soon.