Closed CyberSinh closed 1 year ago
The spaces at the front of the YAML make the default RegExp think it is not valid YAML: https://github.com/DavidAnson/markdownlint#optionsfrontmatter
You can use a .markdownlint.cli2.jsonc
file to customize that RegExp via the frontMatter
property: https://github.com/DavidAnson/markdownlint-cli2#markdownlint-cli2jsonc
Replacing both "---" with "\s*---" in that RegExp will probably do what you want.
Thanks for your answer.
But it doesn't work on my side.
According to regex101.com, the default regex settings should already correctly handle white space between ---
.
Sorry, I was typing quickly on my phone! My advice above was bad. I think this issue may be fixed in the next release of the library which is not yet integrated with the VS Code extension. I'll have a look soon with a "real" computer.
Actually, based on the error message I think this is a duplicate of the following issue: https://github.com/DavidAnson/markdownlint/issues/534
It is a problem with VS Code, not the markdownlint extension.
Hi,
In the code above, the linter complains with message: "No link definition found: 'documentation, support, docs'". The linter should ignore YAML collection in frontmatter of a markdown file.
Thanks.