-
Notifications
You must be signed in to change notification settings - Fork 895
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
Add whitespace (and other markdown-specific) linter for PRs #15
Comments
Perhaps we could at least start with an editorconfig file for all the projects to share? |
Also from @iredelmeier on some PR:
This is one of those tabs vs. spaces discussions that we need to solve with the linter |
Definitely, @SergeyKanzhelev. I just came across markdownlint. Looks like it has support for some of what we want/might want, as well as the ability to add custom rules. Thoughts? |
I'm using markdownlint as a VS Code plugin for my internal projects and found it to be working well so far. I've only been using the default config and didn't add any custom rules or enforce it in our CI yet, though. |
I also use markdownlint for VSCode. If it can be integrated with CI - it's great. As @yurishkuro suggested somewhere before - an option with the automatic formatter will make peoples life way better. Does mardownlint allows this? I believe Yuri was suggesting https://prettier.io/ |
At one of the recent SIG meetings the decision was made to have a soft breaks for whitespaces rule. Also spell check is integrated now. If any other specific linters are required - please file a separate issues. |
Cleanup and clarify config spec
No description provided.
The text was updated successfully, but these errors were encountered: