mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 09:46:01 +03:00
[GH-ISSUE #671] Comments not supported #500
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#500
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PrincessColumbia on GitHub (Dec 7, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/671
Probably more of a feature request as this can probably be set as a custom rule;
Comments in markdown not supported
Per the Markdown Guide, comments can be added to a markdown file using the following syntax:
[comment]: #Example:
[Added to published site 12/07/2022 11:07 am]: #However, markdownlint throws an error:
As this has been tested and peer reviewed, having the definition in the extension by default would be ideal.
Non-critical feature request, issue can be closed if no further feedback needed from me.
@DavidAnson commented on GitHub (Dec 7, 2022):
There is another hack for this which is fairly popular and is already supported.
Context here: https://github.com/DavidAnson/markdownlint/issues/545
Documentation here: https://github.com/DavidAnson/markdownlint/blob/next/doc/md053.md
I think this is a clearer approach than the one you reference and don’t see a need to support both.