Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support EditorConfig for configuration #303

Closed
ejball opened this issue Jul 3, 2020 · 4 comments
Closed

Support EditorConfig for configuration #303

ejball opened this issue Jul 3, 2020 · 4 comments
Labels

Comments

@ejball
Copy link

ejball commented Jul 3, 2020

It would be great if we could configure markdownlint in an .editorconfig file. The syntax could be very similar to the JSON configuration, e.g. the options.config example could look something like this:

[*.md]
markdownlint.default = true
markdownlint.MD003.style = atx_closed
markdownlint.MD007.indent = 4
markdownlint.no_hard_tabs = false
markdownlint.whitespace = false
@DavidAnson
Copy link
Owner

Do you mean for the markdownlint CLI and/or VS Code extension? This library already supports alternate parsers for configuration: https://github.com/DavidAnson/markdownlint#parsers

@ejball
Copy link
Author

ejball commented Jul 3, 2020

Do you mean for the markdownlint CLI and/or VS Code extension?

Yes, sorry about that; should I reopen this case at vscode-markdownlint and/or markdownlint-cli? Does one use the other, or are they independent? (My primary interest is in the VS Code extension.)

@DavidAnson
Copy link
Owner

No worries! They are independent projects, though I own one and am a significant contributor for the other. I think this is most applicable for VS Code, but if there is history of CLI lint tools supporting this file, it would make sense there, too. Thanks!

@ejball
Copy link
Author

ejball commented Jul 3, 2020

Moved to DavidAnson/vscode-markdownlint#120

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants