David Anson

This construct is not part of the CommonMark specification, so it is reasonable for it to be flagged. That said, your example does not seem to generate a violation: https://dlaa.me/markdownlint/#%25m%23%20Issue%20734%0A%0A%5B%5B_TOC_%5D%5D%0A

Thank you! I don't like adding special cases for weird stuff like this, but I see why it's annoying in your scenario. I'll leave this open to think about.

Thanks for the related link. This doesn't look too bad to allow. It's funny these two systems don't even agree on the same syntax for this - tho it's pretty...

Assuming you can identify changelog when invoking the linter, what about running two passes for linting? One pass with that rule disabled and only looking at changelogs, the other pass...

(This library doesn't do anything with globs, it just scans the list of files you give it.)

OK, thanks. I will leave this issue here as a reminder to myself, but this may end up making the most sense in CLI or CLI2.

@stern-shawn, when using this library directly, you can pass it whatever set of files you want and should filter out any you don't. When using markdownlint-cli or -cli2, you may...

As a library, this package only lints the files/strings you pass in to it. If you don't want that file linted, don't pass it in. If you are using this...

I'm not a prettier user and don't have recommendations for how to configure it, sorry.

That scenario is correct and documented: https://github.com/DavidAnson/markdownlint/blob/main/doc/md025.md