[GH-ISSUE #1288] [Feature request] Disable auto correct on save for a specific rule? #657

New issue

Closed

opened 2026-03-03 01:28:49 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 01:28:49 +03:00

Owner

Originally created by @o-l-a-v on GitHub (Jul 9, 2024).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1288

Note

This is about using the extension in VSCode with "default": true in settings.json.

Example rule MD044 "Proper names should have the correct capitalization".

Is it possible to tell Markdownlint to not perform any auto correct on save for one specific rule? Rather than "MD044": false?

If yes: Sorry for creating this issue, I could not find out how from a brief search.
If no: I request this feature.

Originally created by @o-l-a-v on GitHub (Jul 9, 2024). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1288 > [!NOTE] > This is about using the [extension](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint) in VSCode with `"default": true` in `settings.json`. Example rule MD044 "Proper names should have the correct capitalization". Is it possible to tell Markdownlint to not perform any auto correct on save for one specific rule? Rather than `"MD044": false`? * If yes: Sorry for creating this issue, I could not find out how from a brief search. * If no: I request this feature.

kerem

2026-03-03 01:28:49 +03:00

closed this issue
added the
question

fixed in next
labels

kerem commented

2026-03-03 01:28:50 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 10, 2024):

If you have enabled formatOnSave for this extension in VS Code, it will apply fixes for all fixable rules with violations. If you disable a rule via configuration, the extension will not report or fix violations of that rule.

Can you please explain why you want to apply fixes but not for just this one rule?

https://github.com/DavidAnson/vscode-markdownlint?tab=readme-ov-file#fix

@DavidAnson commented on GitHub (Jul 10, 2024): If you have enabled formatOnSave for this extension in VS Code, it will apply fixes for all fixable rules with violations. If you disable a rule via configuration, the extension will not report or fix violations of that rule. Can you please explain why you want to apply fixes but not for just this one rule? https://github.com/DavidAnson/vscode-markdownlint?tab=readme-ov-file#fix

kerem commented

2026-03-03 01:28:50 +03:00

Author

Owner

@o-l-a-v commented on GitHub (Jul 10, 2024):

I'd like this rule to only highlight things. Example, ".NET" is usually capitalized, but not always: https://www.nuget.org/packages/JsonSchema.Net.

Instead of disabling checking for ".NET" it'd be useful with the ability to only highlight/warn.

@o-l-a-v commented on GitHub (Jul 10, 2024): I'd like this rule to only highlight things. Example, ".NET" is usually capitalized, but not always: <https://www.nuget.org/packages/JsonSchema.Net>. Instead of disabling checking for ".NET" it'd be useful with the ability to only highlight/warn.

kerem commented

2026-03-03 01:28:50 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 10, 2024):

Your scenario is supported today by providing the alternate capitalization for the longer form as shown at the bottom of this sample: https://github.com/DavidAnson/markdownlint/blob/main/test/proper-names-projects.md?plain=1

@DavidAnson commented on GitHub (Jul 10, 2024): Your scenario is supported today by providing the alternate capitalization for the longer form as shown at the bottom of this sample: https://github.com/DavidAnson/markdownlint/blob/main/test/proper-names-projects.md?plain=1

kerem commented

2026-03-03 01:28:50 +03:00

Author

Owner

@o-l-a-v commented on GitHub (Jul 11, 2024):

Ah, ok. That's even better! Will try it out.

@o-l-a-v commented on GitHub (Jul 11, 2024): Ah, ok. That's even better! Will try it out.

kerem referenced this issue

2026-03-07 20:06:51 +03:00

[GH-ISSUE #657] Polynomial backtracking in some regexes #2339