mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 09:16:02 +03:00
[GH-ISSUE #174] no-trailing-punctionation rule being ignored #151
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#151
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 @yankeeinlondon on GitHub (Mar 23, 2019).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/174
in my
.markdownlint.yamlfile (in repo root) I have several rules (see below) which all work but I wanted to modifyno-trailing-punctuationto allow both "!" and "?"But as many combinations as I try I can't get this configuration adjustment to take hold. Also of note, I am using the
vs-codeenvironment to surface these warnings and so therefore possibly this is actually an error with themarkdownlintextension by David Anson. I will raise this issue there too as I'm really not sure how to distinguish between the two.@DavidAnson commented on GitHub (Mar 23, 2019):
punctuationis a parameter to the rule, as seen here in JSON:github.com/DavidAnson/markdownlint@2710c375b3/test/heading_trailing_punctuation_customized.jsonYou need to set it as a parameter in YAML as seen here for
indent: https://github.com/DavidAnson/markdownlint/blob/master/test/config/config-grandparent.yamlIf that’s not clear, I can give a better example when I’m not on my phone.
@yankeeinlondon commented on GitHub (Mar 23, 2019):
Many thanks @DavidAnson, that is clear. So for others who may end up here, in YAML I would configure this rule as:
@DavidAnson commented on GitHub (Mar 25, 2019):
Yep!