starred/markdownlint

Fork 0

mirror of https://github.com/DavidAnson/markdownlint.git synced 2026-04-25 01:05:55 +03:00

[GH-ISSUE #41] Add rule to check for file naming #33

New issue

Closed

opened 2026-03-03 01:23:10 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 01:23:10 +03:00

Owner

Originally created by @pascalberger on GitHub (Jan 11, 2017).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/41

Adding a rule to check for file naming would be a nice enhancement.

Guidelines which for example we currently are using:

Filename needs to be lowercase
Allowed characters: a-z 0-9 - .

Originally created by @pascalberger on GitHub (Jan 11, 2017). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/41 Adding a rule to check for file naming would be a nice enhancement. Guidelines which for example we currently are using: * Filename needs to be lowercase * Allowed characters: `a-z 0-9 - .`

kerem

2026-03-03 01:23:10 +03:00

closed this issue
added the
new rule
label

kerem commented

2026-03-03 01:23:11 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jan 11, 2017):

To be clear, you are referring to the names of the Markdown files that are parsed for content, right? If so, this feels a bit on the edge of what I think a Markdown linter should do. But I will think about this more.

@DavidAnson commented on GitHub (Jan 11, 2017): To be clear, you are referring to the names of the Markdown files that are parsed for content, right? If so, this feels a bit on the edge of what I think a Markdown linter should do. But I will think about this more.

kerem commented

2026-03-03 01:23:11 +03:00

Author

Owner

@pascalberger commented on GitHub (Jan 12, 2017):

Yes, I was referring to the *.md files. I see the point that this is not a typical use case for a linter, since it is no longer about the content. On the other hand, considering a repo containing some source and Markdown documentation, it still has to do with the Markdown part :)

@pascalberger commented on GitHub (Jan 12, 2017): Yes, I was referring to the `*.md` files. I see the point that this is not a typical use case for a linter, since it is no longer about the content. On the other hand, considering a repo containing some source and Markdown documentation, it still has to do with the Markdown part :)

kerem commented

2026-03-03 01:23:11 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jan 12, 2017):

Got it.

What about something like this instead: https://www.npmjs.com/package/gulp-check-file-naming-convention

Or maybe:
https://www.npmjs.com/package/check-filename

@DavidAnson commented on GitHub (Jan 12, 2017): Got it. What about something like this instead: https://www.npmjs.com/package/gulp-check-file-naming-convention Or maybe: https://www.npmjs.com/package/check-filename

kerem commented

2026-03-03 01:23:11 +03:00

Author

Owner

@pascalberger commented on GitHub (Jan 18, 2017):

Thinking a little bit more about it, doing these checks outside might be the better solution than duplicating existing functionality here.

@pascalberger commented on GitHub (Jan 18, 2017): Thinking a little bit more about it, doing these checks outside might be the better solution than duplicating existing functionality here.

kerem commented

2026-03-03 01:23:11 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jan 19, 2017):

Great.

@DavidAnson commented on GitHub (Jan 19, 2017): Great.

kerem referenced this issue

2026-03-07 20:02:19 +03:00

[GH-ISSUE #33] Shareable configs #1874