Customizing plugins, other options with VSCode extension

[heaths]

Customizing plugins, other options with VSCode extension

[DavidAnson]

Fundamentally, you are trying to use a Markdown linter on something that isn’t (yet) complete Markdown. Per my comment in the other issue, I think it’s better in the abstract to lint the final document.

Leaving that aside, what I think you are proposing is to create a markdown-it plugin that fills in the referenced content at parse time. It is possible to use such plugins with the VS Code extension, but it’s not a strategy I would recommend because I’m moving away from the markdown-it parser. The two rules you are concerned about have already been migrated, so this would not help.

I do not think this is a common problem, so I am reluctant to add infrastructure for it. I don’t know of any other linters that support this kind of thing, but would be happy to review links if there is precedent.

If you are using the library directly, then instead of passing it files, you could perform the transformation yourself and have it lint those strings instead.

Or if I’ve misunderstood the proposal, please let me know!

[heaths]

I totally appreciate it. It was a long shot and not critical nor do I have time to work on a solution. I appreciate the thought!