Support the .markdown extensions when filtering for files directly.
The longer .markdown is actually the one endorsed by John Gruber, Markdown's creator. There are other extensions in use, as well, but I think these two are fine for nowsince they're by far the most used and are what GitHub supports as
well.
Support directories in config-provided include_paths
Without this, only Markdown files in the root directory would ever be analyzed. Which is most Markdown, certainly, but not all.
@jpignata I forked markdownlint & implemented built-in support for the *.markdown extension there. I've opened a PR for that work, but since the parent repo has been quiet for a few months, I've switched this engine to use my fork in the interim.
Support the
.markdown
extensions when filtering for files directly.The longer
.markdown
is actually the one endorsed by John Gruber, Markdown's creator. There are other extensions in use, as well, but I think these two are fine for nowsince they're by far the most used and are what GitHub supports as well.Support directories in config-provided
include_paths
Without this, only Markdown files in the root directory would ever be analyzed. Which is most Markdown, certainly, but not all.