Markdown Validation

I’m trying to integrate some basic markdown parsing / validation in my build process which is used to validate a hand-written CHANGELOG.md file. From time to time I see colleagues make small mistakes where I wish I’d have a tool that would automatically flag these issues and break my build, things like invalid links (Foo(https://...) instead of ([Foo](https://...)), missing whitespace (-something instead of - something), stuff like that.

Is there any kind of “strict” option in the parser that I missed where the parser would bail out on inconsistencies / issues like this? If not, would it be feasible to implement such a thing or is the markdown spec too loose for any validation check?

[vsch]

@realdadfish, as a future implementation you can make the rules extensible so that a RegEx based validator is available and applied to Node via Node.getChars(), other node specific validators can be RegEx based or code based for maximum flexibility and would specify node classes to which they apply.

Then the configuration would consist of configuring a list of rules and visiting the document.

[realdadfish]

OK, thanks for the pointers, I’ll see with what I can come up with. Will close this for now. Thanks again!