search

DavidAnson / vscode-markdownlint

Markdown linting and style checking for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint
MIT License
946 stars 172 forks source link

MD013 line-length not automatically fixed by formatter #348

Closed epneo-sebastianbaier closed 3 months ago

epneo-sebastianbaier commented 3 months ago

Hi,

because of the issue #105 and your recommendation there:

If you want the best compatibility between this extension and a CLI, you’ll have the easiest time using the markdownlint CLI written in/for Node.js: https://github.com/igorshubovych/markdownlint-cli

I'm now moving from mdl for markdownlint-cli for our pre-commit hooks. However, it seems the violations of MD013 line-length are not fixed automatically by the VSCode extension if used as formatter. Shouldn't this be automatically fixed, as written on the VSCode extension page?

All of a document's violations of the above rules can be fixed automatically.

If I disable MD013 in my .markdownlint.jsonc it is no longer reported by the VSCode extension and the pre-commit is also not throwing an error, but if enabled both are recognizing the MD013 violation. So the configuration file is detected correctly by the VSCode extension and markdownlint-cli.

Greetings Sebastian

DavidAnson commented 3 months ago

MD013 is not in the referenced list of rules that are automatically fixed.

epneo-sebastianbaier commented 3 months ago

Thx, I thought so and it was just a misunderstanding, because both lists (automatic fixable and not) are above the text:

All of a document's violations of the above rules can be fixed automatically.

DavidAnson commented 3 months ago

I'll try to make this more clear in the documentation.