David Anson

I've thought about how to do this for line scope and the challenge is that problems quickly arise with how/where to add the suppression comment: Adding `markdownlint-disable-line` to the end...

For folks complaining about the performance hit of the `Options.gitignore`, my understanding of the current implementation is enabling that option adds a blocking preprocessing step that enumerates and parses potentially...

> On our codebase: > 1. using `gitignore: true`: > ~8sec > 2. custom: > ~100ms > ~8000% difference is a lot... FYI, this is not an apples-to-apples comparison as...

For scenarios where only the root `.gitignore` file matters, setting `Options.ignoreFiles` to `".gitignore"` should be very fast as it should avoid the (correct by specification!) `**` part of the default...

Link to the issue you opened yesterday: https://github.com/DavidAnson/vscode-markdownlint/issues/307 I replied yesterday as well.

FYI, SuperLinter uses https://github.com/igorshubovych/markdownlint-cli which uses https://github.com/DavidAnson/markdownlint, not this project. Here is the corresponding issue for that project: https://github.com/DavidAnson/markdownlint/issues/457

This makes sense and should be pretty straightforward since it can use the parser output for links directly. There is precedent in existing rules for analyzing link content that could...

There are two parts to achieving this. The first is done by the issue linked above. The second is described by me here: https://github.com/igorshubovych/markdownlint-cli/pull/457#issuecomment-1945283551

I don't think this issue is resolved: the `projectConfigFiles` array still only contains JSON/YAML files.

FYI, this is possible now with markdownlint-cli2: https://github.com/DavidAnson/markdownlint-cli2