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

Determine if there is a good way to "validate" Markdown #27

Open
jacebrowning opened this issue Mar 24, 2014 · 2 comments
Open

Determine if there is a good way to "validate" Markdown #27

jacebrowning opened this issue Mar 24, 2014 · 2 comments

Comments

@jacebrowning
Copy link
Member

jacebrowning commented Mar 24, 2014

During Item validation, see if we can check for common formatting mistakes:

# mismatched formatting
**word*

# missing list separator
invalid list:
  - item1
  - item2

@jacebrowning jacebrowning added this to the backlog milestone May 30, 2014
@jacebrowning jacebrowning modified the milestones: backlog, v0.10 Oct 29, 2014
@jacebrowning jacebrowning modified the milestones: v0.10, backlog Jan 29, 2015
@ngbrown
Copy link

ngbrown commented May 13, 2018

There is a markdownlint implemented in Ruby. A Node.js version builds on those rules.

A Python version was started, but didn't get very far.

If the files being edited were .md files, then the editors have plugins that will highlight errors while typing. (ex. Visual Studio Code, Sublime, or Atom).

While Sublime plugins are Python based, the Sublime markdown linter actually shells to the Node.js version, which has to be installed separately. That would be an option for checking at the command line, especially imported text.

@jacebrowning jacebrowning removed this from the backlog milestone Jun 27, 2019
@neerdoc
Copy link
Collaborator

neerdoc commented Mar 9, 2022

Standard Markdown (without plugins) is quite limited. It should be relatively straight forward to write few lines of regexp to validate it.

@neerdoc neerdoc added this to Inbox in Work via automation Mar 9, 2022
@neerdoc neerdoc added this to the v2.4 milestone Mar 9, 2022
@neerdoc neerdoc moved this from Inbox to To do in Work Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Work
To do
Development

No branches or pull requests

3 participants