-
Notifications
You must be signed in to change notification settings - Fork 49
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
Feature Request: Conform to Markdown Linters #101
Comments
jsdoc2md outputs Github-flavoured markdown.. does the linter above support GFM? |
Yes, I believe. I don't know all the rules fully by heart, so it's possible there might be a few rules it doesn't. But it does seem so from me testing my own MD file. |
If you have GFM issues, you could always try the |
I personally consider this low priority - it would be a considerable amount of work for not enough meaningful gain.. happy to accept PRs though. Will close for now as it's not a feature in demand. |
Re-opening.. it may take some time (given the complexity of the existing handlebars solution) but I will aspire to at least pass a GFM linting test.. I have made a start. I'm not sure how many of the existing linting errors, for example those that complain about embedded HTML, can be fixed but I will take a look.. When this tool was created in 2014, things like HTML links were necessary to support both Github and the NPM website but things may have changed since. |
It would be really cool for this plugin's output to be able to conform to markdown linters, such as this one https://github.com/DavidAnson/markdownlint.
The text was updated successfully, but these errors were encountered: