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

Markdown Linting #283

Open
3 tasks done
VijaySharma815 opened this issue Sep 18, 2022 · 1 comment
Open
3 tasks done

Markdown Linting #283

VijaySharma815 opened this issue Sep 18, 2022 · 1 comment
Labels
Check Later Check this Issue later

Comments

@VijaySharma815
Copy link
Contributor

VijaySharma815 commented Sep 18, 2022

Prerequisites

  • I checked the documentation and made sure this feature does not already exist.
  • I checked the existing issues to make sure this feature has not already been requested.
  • I have read the code of conduct before creating this issue.

Problem

Standards and consistency of Markdown files

Feature / Solution

Rules to enforce standards and consistency for Markdown files.

  • Command to check the markdown files
  • Auto fixes

Please see this:

Alternatives

No response

Additional Context

No response

@VijaySharma815
Copy link
Contributor Author

We tried two packages:

mdformat: This tool seems to make several mistakes including not recognising the admonitions by mkdocs and some strange line breaking in History.md. Due to its automatic nature, markdown file lining needs to be 100% correct without needing manual changes which do not seem to be the case for this too.

Therefore, unless through configurations we can get it working without any errors.

makrdownlint: This tool requires the introduction of a heavy dependency, either npm and associated JS dependencies, or docker.

@5A11 5A11 added the Check Later Check this Issue later label Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Check Later Check this Issue later
Projects
None yet
Development

No branches or pull requests

2 participants