Custom rule IDs are flagged in .markdownlint.json when opened in editor
See original GitHub issueCame across this as part of https://github.com/microsoft/vscode-docs-authoring/pull/747 When you disable custom rules in your markdownlint config like
{
"default": true,
"DOCSMD001": false,
"DOCSMD010": false,
"DOCSMD011": false,
"MD001": false,
"MD004": false,
...
The custom rule IDs are flagged as Property DOCSMD001 is not allowed.
Is there a proposed why to make the schema validation happy for custom rules?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
markdownlint-cli2/README.md at main - GitHub
A fast, flexible, configuration-based command-line interface for linting Markdown/CommonMark files with the markdownlint library ...
Read more >How do I change Markdownlint settings in Visual Studio Code
In Visual Studio Code, open File -> Preferences -> Settings or use CTRL + , · Edit the User Settings tab on the...
Read more >Coc linting - Caritas Castellaneta
12. json (opens new window). coc-pyright. nvim neomake - Asynchronous linting ... the bundled rules and your custom rules to fit the needs...
Read more >Documentation: MultiQC
Custom run name. When you launch nextflow, you can use the -name command line flag (single hyphen) to give a name to that...
Read more >Index · Documentation · Development · Help · GitLab
Site architecture - How https://docs.gitlab.com is built. ... These rules are configured in the .markdownlint.json files located in the root of four repos ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This will be fixed in the next release by this update to the library: https://github.com/DavidAnson/markdownlint/commit/6061cce169ecf8820cd8cd0b9f1c6570ebb3dafe
Confirmed it isn’t giving the warning in the Problems tab. Thanks!